Why use artifacts
- Work does not stay trapped in a chat. What an agent wrote is a file you can open tomorrow, from any device.
- One link, always current. You do not chase “final-v3”. The link shows the latest version.
- Other agents can read it. The same link gives an agent the plain text, so it does not have to scrape a page.
- You can see what changed. With history on, earlier versions are kept and you can compare them.
Example. A consultant asks her agent for a market summary. The agent saves it as a document and gives her the link. She fixes two paragraphs in the browser. The next day another agent reads the same link and builds the slides from her corrected text.
Save work and get a link
An agent saves text (a document, a web page, code, data, a chart) or uploads a file such as an image or a PDF. Tokenrip shows each kind in a fitting way: a document is formatted, code is highlighted, a web page is rendered. A file lives in one of two places:- In a workspace, where everyone in the workspace sees it.
- On its own, owned by one account. Its owner shares it with a team, or by its link.
Example. A dev team’s agent writes the release notes and saves them in the team’s workspace. Everyone on the project finds them under Files.
Update it at the same link
A file here works like a file on a computer. A new save replaces the content, and the link does not change. An agent can replace the whole file, add text at the end, or change one passage without sending the rest.Example. An online shop’s agent keeps a running log of supplier price changes. Each day it adds a few lines at the end of the same file. The buyer always opens the same link.
History
By default a save keeps nothing of the version it replaces. Turn history on to keep earlier versions:- Off: only the current content is kept.
- Keep the last: a number of earlier versions, from 1 to 100.
- Keep all: every version.
Example. A finance team sets “Keep all” on its Reports folder. When a number in the quarterly report looks different, they open Changes and see which save altered it.
Edit it yourself
You can edit a text file in the browser: open it, change it, and save. Your save is a new version, like an agent’s. In a workspace, an agent cannot replace a whole file that someone else wrote last unless it has seen that content. If you edited the file after the agent read it, the agent’s save is refused and it reads your version first.Share one file with anyone
A workspace file starts private to the workspace. An editor can turn on its public link. Then anyone with the address reads that file without signing in, its earlier versions included. It is never listed or searchable for outsiders, and they see nothing else in the workspace.Example. An agency finishes a campaign report in the client’s workspace. The account manager sets the report to Public and sends the link to the client’s CEO, who has no account.
Make your own copy
Forking a file makes a separate copy that you can change without touching the original. The copy says “Forked from” with a link back. Later changes to the original do not reach the copy.What you see
- Files in a workspace’s panel, pinned files first. + uploads files or adds a document or a folder.
- A file’s page: the content, with editing for text files, Changes, and the tasks the file is part of.
- A file’s menu: Rename, Move to folder, Pin artifact and Version history….
- The Public link chip: Private or Public.
- Storage, in your avatar’s menu: what you use against your plan’s limit.
Ask your agent
- “Save this report to the client workspace and give me the link.”
- “Change the status line in the launch plan to ready.”
- “Keep the last five versions of the pricing document.”
- “What changed in the proposal since yesterday?”
- “Make a copy of the onboarding guide that I can adapt for the new client.”
Good to know
- An uploaded file such as an image or a PDF can be up to 10 MB.
- Earlier versions are kept only if history is on. With history off, a replaced version is gone.
- Adding text at the end of a file never keeps the earlier version, even under Keep all. The earlier content is still there, as the start of the new one.
- Every kept version counts toward storage. So does anything in the trash.
- Deleting a file moves it to the trash for 30 days. Deleting one version is immediate and permanent.
- A public link also shows the file’s earlier versions. Remove the ones you do not want read before you turn it on.
- A table cannot be forked and keeps no versions.
For agents and developers
Artifact rules
Types, versions, history, aliases, forking and deletion
CLI: artifacts
The artifact commands
API: artifacts
The routes, bodies and refusals