# Stop describing the prototype. Send it.

For product teams. Your agents build prototypes, specs and dashboards. Publish them to one private workspace, share a link that works in any browser, and every change lands on the same link.

## Screenshots don’t click.

The prototype runs on one laptop, the recording sits in Slack and the spec has five copies. Here’s the swap.

- The prototype runs on one laptop. With artifact.guru: It runs at a link anyone on the team can open.
- A screen recording loses every click. With artifact.guru: Buttons, filters and flows keep working.
- Five versions, five links. With artifact.guru: One link. Every change is a new version on it.
- User tests stall on accounts and setup. With artifact.guru: Send a secret code. Testers open it in a browser.

## From the agent to the review in four steps.

1. **Build it with your agent.** Claude Code, Codex, Gemini CLI or ChatGPT. A prototype, a spec, a dashboard.
2. **Publish to the team.** Say “publish this.” It lands private, where your workspace can open it.
3. **Share it for review.** Invite stakeholders by email, or give testers a secret code.
4. **Ship the next version.** Fixes land on the same link. Roll back if the new one breaks.

### Many agents, one file.

Claude Code builds it. Codex handles the edge cases. ChatGPT tightens the copy. All on the same artifact.

- Any agent finds the file and saves a new version.
- Edits never overwrite each other.
- Works with any app that can add an MCP server.

### Every change is a version.

Whoever opens the link sees the latest. Every version says who made it, and with which agent.

- Edit HTML and Markdown in the browser, or ask your agent.
- Roll back, and the link shows that version right away.
- The link never changes.

### Prototypes that still work.

React apps, HTML pages and whole built sites run in the browser, on a separate, sandboxed address.

- Drag in a build folder and it becomes one artifact.
- Specs in Markdown, with Mermaid diagrams.
- Up to 100 MB a file, 250 MB on Team.

### Private to the team. Open for the test.

Everything starts private to your workspace. Invite a stakeholder by email, or give testers a secret code.

- Secret codes expire in 7 or 30 days, or never.
- Invited links show who opened them.
- Shared links ask search engines not to index them.

## Start with one prototype.

Free covers 3 live links. Team is $30 a month for 3 editors, then $8 each.

## Questions

### Does it work with Claude Code and Codex?

Yes. Add one address, approve once in your browser, and say “publish this.” Gemini CLI and Grok work the same way. ChatGPT works in developer mode on Business, Enterprise or Edu.

### Can I publish a whole React app?

Yes. Drag in the built folder, or a zip of it, and it becomes one artifact. A single React component works too.

### Can people comment on the prototype?

Your team and anyone you invite by email can, beside the prototype, and your agent can read the comments and publish the fix to the same link. Testers on a secret-code link don’t see comments, so collect their notes the way you already do.

### Who can see our work?

Only your workspace, until you share it. Then pick email invites, a secret code or public, link by link.

### Is it safe to publish code?

Pages, React apps and sites run in a sandbox on a separate address, with no access to the viewer’s account.

Start free: [Create an account](https://artifact.guru/sign-up). Connect an agent: [Setup for each agent](https://artifact.guru/docs/connect).

Source: https://artifact.guru/for/product-teams