An artifact is a single live app, readable document, or versioned file that people and agents edit together. It has one stable address and one History rather than behaving like a copied file in a folder. Everyone opening it sees the current version, and agents update it through real version history instead of regenerating copies.
Why is an artifact different from a file?
Files are downloaded, edited, returned, and multiplied into competing versions. An artifact cannot be copied accidentally: all changes enter the same History at one URL. A wrong change is recovered by restoring an earlier version.
What properties does every artifact have?
| Property | Meaning |
|---|---|
| Address | Stable artifact URL. |
| Type | App, document, or asset, determining rendering. |
| Owner | Person who created or claimed it. |
| Team | Team that owns it. |
| Visibility | Private to the team or published. |
| History | Every change with author and message. |
Addresses look like app.agentgrid.io/artifacts/Ez-CDDsmYLaApCIqpPv5bQ. A human should copy the real URL from Share instead of constructing it.
What ownership and visibility states exist?
- Anonymous: created by an AI that never connected. Anyone with the link can view it, but it is read-only, owned by nobody, and expires 24 hours after creation.
- Claimed: owned by a team, editable, and no longer expiring. Connected assistants create directly in this state.
- Published: deployed to a public URL available without an account. Publishing is separate from sharing and always explicit.
What can an artifact contain?
- App: a live web page such as a presentation, dashboard, calculator, form, or game. Its hub card has a live preview thumbnail.
- Document: one or more markdown files rendered readably and editable in the rich editor.
- Asset: any other file. Assets are stored, versioned, shareable, and agent-readable without a preview. AgentGrid.io explicitly reports unavailable rendering rather than showing a broken frame.
Any experience buildable with HTML can be an app, including:
| Work | Study and teaching | Personal |
|---|---|---|
| Slide deck or presentation | Quiz or flashcard set | Trip itinerary with map |
| Dashboard or live-chart report | Interactive lesson or explainer | Budget or savings tracker |
| Pricing or ROI calculator | Revision timeline | Recipe collection |
| Landing page or one-pager | Lab-results write-up with charts | Wedding or event invitation |
| Project timeline or roadmap | Clickable concept diagram | Portfolio or CV |
| Survey or intake form | Study planner | Countdown or checklist |
| Directory or comparison table | Citation and reading list | Photo gallery |
A presentation built as an app stays at one browser address, updates in place, and does not need to be resent.
Technical constraints
- An app requires
index.html; without it the page is blank. - A document requires at least one
.mdfile. - App source is changed through a connected AI or Edit with AI. Document content can also be edited directly in the app.
- A complete codebase can be one artifact. Ask a connected AI to push source and assets, excluding
node_modulesand build output. In-app Import from ZIP is coming soon. - An artifact resembles a project but is not a synced folder; it is one live thing with one address.
Deletion and collaboration semantics
- Deletion removes the artifact and all History permanently. Restore only rolls content back and preserves History.
- Multiple agents can edit the same artifact, with each agent's changes recorded separately by name.