An artifact is a set of files that MySpec stores and versions as one unit,
such as a clickable website prototype made of index.html, css/site.css and
js/app.js. Every change adds a new revision; earlier revisions stay in the
artifact’s history.
Artifacts come from two places:
- A Website artifact session builds one from a conversation, and an Edit website artifact session changes it.
- Agents create and update them through the MCP tools.
If your project has no Artifacts tab, artifacts are not available in your workspace yet.
Find a project’s artifacts
- The Artifacts tab lists every artifact of the project, the most recently updated first, with its latest revision and when it changed. Select one to open it in the viewer. Select Show more to load older ones.
- The ARTIFACTS section of the sidebar appears in a chat and on the project pages once the project has at least one artifact. It lists the newest ones with their revision, such as v4, and highlights the artifact the current chat works on. Each one opens in a new tab, so the chat you are in stays where it is. When the project has more than the section shows, select View all to open the Artifacts tab.
View an artifact
The viewer shows an artifact’s latest revision in three tabs:
| Tab | What it shows |
|---|---|
| Preview | The site running in an isolated frame. Pick a Preview width (Desktop, Tablet (768 px) or Mobile (375 px)), select Reload to start it again, or Open in new tab to see it full size. |
| Source | Every file of the revision with its size and type. Long lines wrap, so a file written as one line stays readable. Files larger than 1 MB and files with no text view, such as images, are not shown. |
| History | Every revision, newest first, with who made it (a person or the AI), its file count, size and message. Select a revision to preview it, or Show the latest to go back to the newest one. |
Select Refresh to load revisions written since you opened the viewer, and Download ZIP to download all the files of the revision you are viewing.
Restore an earlier revision
In History, select Restore next to a revision. MySpec adds a new revision with that revision’s files, so nothing is lost: the newer revisions stay in the history and you can restore one of them later. If someone else changed the artifact since you opened it, the viewer shows the latest revision instead; check it and try again.
Change an artifact with AI
On the latest revision, select Edit with AI to start an Edit website artifact session for this artifact. Describe the change; each change is stored as a new revision that you preview and then keep or discard.
When a Website artifact session finishes, its completion card offers Edit with AI too.
Watch the AI write the files
While a website session writes the site, the chat shows a short line for each file, such as Writing css/site.css · ~12.0 KB, that updates as the file grows and then reads Wrote css/site.css. A file that could not be written reads Could not write, and one the session stopped in the middle reads Stopped writing. Before each file the AI also says in one sentence what it is writing.
These lines are shown only while the session runs. When you open the chat later, the revision card shows what was stored.
Mention an artifact in a chat
Point the AI at an artifact in any chat, Generate, Edit or website:
- Type
@in the message box, or select Reference a file. - Open the Artifacts section of the list. It shows each artifact with its latest revision. Type part of a name to filter it.
- Choose an artifact with the mouse, or with the arrow keys and Enter.
The artifact appears as a chip in your message, and your sent message shows its name and revision, such as FlashPay · v4. The mention means the revision you saw when you sent the message; the AI reads the latest one when you ask for it.
The AI reads the artifact’s files when it needs them. It cannot change an artifact from a mention: only a website session or an agent writes revisions.
Link an artifact from a spec file
A spec file can link to an artifact with a normal Markdown link whose address
is artifacts/ followed by the artifact’s slug:
## Payment screen
See the clickable prototype:
[FlashPay customer prototype](artifacts/flashpay-customer-prototype)The slug is the artifact’s short, stable name. It does not change when the artifact is renamed, so the link keeps working. The link always opens the artifact’s latest revision.
In the spec file viewer and in chat replies, the link shows as an artifact marker. Select it to open the artifact in a new tab.
- A link to a slug the project has no artifact for stays an ordinary link.
Specs for an existing codebase often link to a real
artifacts/folder, and those links keep working as before. - On a share link, the marker shows the artifact’s name without a link. People with a share link can read the spec files, not the artifacts.
You rarely need to write these links yourself. In a Generate or Edit session, the AI links the matching prototype when it writes a section about screens, pages or user flows. To add one, ask, for example “Link the FlashPay prototype in the payment screen section”.
What the AI can do with artifacts
While the project has at least one artifact, the AI in every session can:
- List the project’s artifacts, with a ready-made link for each one.
- List an artifact’s files and read the text files, a page at a time.
- Add artifact links to the spec files it writes.
Spec sessions only read artifacts; they never change one. In a project with no artifacts, the AI is not offered these abilities at all.
Who can do what
| Action | Read | Write | Admin |
|---|---|---|---|
| See the Artifacts tab, preview, source and history | Yes | Yes | Yes |
| Download a ZIP | Yes | Yes | Yes |
| Restore an earlier revision | No | Yes | Yes |
| Start Edit with AI | No | Yes | Yes |
| Mention an artifact in a chat | No | Yes | Yes |