Valet|Docs
Sign up

Valet Documentation

Valet is a platform for sharing, collaborating on, and hosting the work you create with agents — Claude Code and Cowork, ChatGPT and Codex, Cursor, and anything else that speaks MCP.

  • Artifacts save and share interactive webpages with your team, on a URL you control, with access gated.
  • Agents save the workflows and tasks you complete in an agent, and can build their own interfaces — artifacts, Slack bots, email addresses, and MCP servers.
  • Integrations give artifacts and agents access to your data and processes, so they get work done and keep things up to date.
  • Teams let you invite and manage who you collaborate with.

This documentation covers what artifacts and agents are, the dashboard where your team works with them, and the Valet skill and CLI that drive it all from your coding agent.

Quick Start

1. Connect your agent

You do not install anything first. If your agent has a terminal — Claude Code, Codex, or Cursor — copy the instructions below and hand them over. The instructions route themselves: the agent installs the Valet plugin where its harness has one, the skills where it does not, and then publishes. That is the fuller path — whole folders, later updates, and agents too.

Free to try · No signup required

No terminal? Claude Cowork, claude.ai, and ChatGPT have no shell to install anything into. Add Valet's MCP server as a connector instead, and the same publishing tools show up in the conversation:

https://api.valet.dev/mcp

It needs no account either — connect it and ask. Signing in through the connector publishes into your organization instead. See Connect Your Agent for the exact steps in each client, and MCP Server for the tools it exposes.

2. Ask for something worth sharing

Ask your agent for a dashboard, a research brief, a postmortem, a prototype — anything that renders in a browser. When it finishes, it publishes the result and gives back a live URL you can send to anyone. With the skill it runs valet deploy; over MCP it calls publish_site. Either way you get an address.

3. Claim the artifact

That first URL is anonymous: public, free, and no account required. It is also temporary — anonymous artifacts are removed 36 hours after they are created. Alongside the URL your agent prints a claim link. Open it, sign in or sign up, and pick the organization the artifact should live in.

Claiming makes the artifact permanent, moves it to your org's namespace (<artifact>.<org>.valet.run), and makes it private — visible to your teammates once they sign in, and to nobody else until you say otherwise.

4. Bring your team

Everything after that happens in the dashboard: invite teammates, change who can see an artifact, and build agents that keep the work up to date on their own.

Where to go next

  • Connect Your Agent — the install or connector step for each client, one at a time.
  • Artifacts — what an artifact is and why you would publish one.
  • Agents — turning a workflow you ran once into one that runs on its own.
  • Dashboard — where your team manages artifacts, people, and agents.
  • MCP Server — publishing from an agent with no terminal.
  • Valet CLI — the command line behind all of it.