Artifacts
An artifact is a webpage — or a whole folder of them — published to a URL your team can open. It is where the work your agent just made goes to live, instead of dying in a terminal scrollback, a screenshot, or a zip file nobody can open.
Ask any agent — Claude Code or Cowork, ChatGPT or Codex, Cursor, anything that speaks MCP — for a report, a dashboard, or a small tool, and it can publish the result itself. You get back an address, not an attachment.
Why publish an artifact
- Your coworkers can actually open it. An interactive page needs a browser, not a chat window. A link works on a laptop, on a phone, and in a meeting.
- It stays findable. The address belongs to your organization — <artifact>.<org>.valet.run — so the thing you shared last month is still there this month, at the same place.
- Access is a setting, not a scavenger hunt. Private to your team, password-protected for people outside it, or public to anyone with the link. Change it whenever you like.
- It can be updated. An artifact is a living page. You — or an agent — can redeploy it with fresh numbers without changing the URL.
What people publish
Anything that renders in a browser: dashboards and data explorers, research briefs, vendor comparisons, postmortems, runbooks, brand guides, offsite plans, prototypes, one-off internal tools, slide decks, PDFs, and images. If your agent can produce it, Valet can host it.
Who can see it
- Private — the default. Only members of your organization, after signing in. When someone leaves your team, they lose access; there are no stray share links to hunt down.
- Password — your team, plus anyone who has the password. Made for people outside the company who will never have a Valet account.
- Public — anyone with the address.
Every request is recorded, so you can say who opened what and when. Changing the access mode takes effect immediately and signs current visitors out.
Trying it without an account
Your first artifact needs no signup. An anonymous artifact gets a public URL in seconds and is removed 36 hours later unless you claim it. Claiming asks one question — which organization it belongs to — and then the artifact is permanent, private, and yours to manage.
How artifacts get published
- From your coding agent. Give Claude Code, Codex, or Cursor the prompt from the Quick Start. It installs the Valet skill, publishes the folder, and prints the URL. This is how most artifacts get made, and it is the fullest path.
- From an agent with no terminal. Claude Cowork, claude.ai, and ChatGPT cannot install a CLI. Connect Valet's MCP server instead and they publish from inside the conversation.
- From an agent you built. An agent can publish and update an artifact as part of its job — a dashboard that refreshes every morning, a status page that reflects what just happened.
- From the command line. Publish a directory yourself, with no AI involved: see the CLI reference.
Once an artifact exists, your team manages it from the dashboard.