Build

Get started

What you need#

• An AI agent you already use, such as Claude Code, Codex, Cursor, claude.ai or ChatGPT. You ask it to publish, and it does the work.
• A Valet account and an organization. An organization is the shared workspace where your team's work lives. Sign up at dashboard.valet.dev, and name your organization when setup asks. If a teammate invited you, join their organization instead.

You'll publish an artifact: a web page or small website, such as a report or a dashboard, at its own address.

Connect your agent#

The quickest way is to give your agent these instructions. It installs what it needs, publishes what you're working on, and replies with the link:

The instructions set up Valet's cloud. For your company's own installation, see Use your company's installation.

To connect by hand, the way depends on whether your agent can run commands on your computer.

A skill is a set of instructions your agent reads to learn Valet. Your team can publish its own skills too; see Skills. An MCP server gives an AI app new tools. The Valet CLI is the valet command that agents use when they can run commands.

Claude Code#

Type these in Claude Code:

/plugin marketplace add valetdotdev/skills
/plugin install valet@valet

Codex#

Run these in a terminal:

codex plugin marketplace add valetdotdev/skills
codex plugin add valet@valet

The plugin adds the Valet skills and connects Valet's MCP server.

Other agents that run commands#

npx skills add valetdotdev/skills -g

This adds only the skills, which publish with the Valet CLI. The first time your agent needs the CLI, it asks before it installs it.

claude.ai, ChatGPT and other chat apps#

In your chat app's settings, add a custom connector with this address:

https://api.valet.dev/mcp

The first time the chat app uses Valet, it opens a Valet sign-in page. Chat apps publish text files only: HTML, CSS, JavaScript, Markdown, JSON and SVG. A page with images or PDFs needs an agent that runs commands.

Publish your first artifact#

Ask your agent to make something and publish it:

Make a one-page summary of this week's support tickets and publish it
with Valet as support-summary.

What happens next:

1. The first time, your agent opens a browser so you can sign in to Valet.
2. The artifact goes into your organization. If you belong to more than one organization, tell your agent which one to use.
3. Your agent replies with the artifact's address, such as https://support-summary.acme.valet.run.
4. The artifact starts private. Only members of your organization can open it, after they sign in to Valet. To share it with a teammate, send them the address.

In a new organization, the first address can take a few minutes to start working while Valet sets up HTTPS.

Your agent publishes through Valet's MCP server, or with the CLI when it runs commands. Both call an artifact a site:

publish_site
{
  "name": "support-summary",
  "title": "Support summary",
  "description": "This week's support tickets on one page.",
  "files": [{ "path": "index.html", "content": "<!doctype html>\n…" }]
}

Over MCP, the sign-in page opens the first time your agent calls a tool. With the CLI, valet auth login opens it.

Use your company's installation#

Sign in to your company's Valet dashboard first, and create or join your organization. Then set these in the terminal you start your agent from, with the values your administrator gives you:

export VALET_API_URL=https://api.<domain>
export VALET_GATEWAY_URL=https://gateway.<domain>
export VALET_WORKOS_CLIENT_ID=<client ID>
export VALET_CONFIG_DIR=~/.config/valet-<company>

So every new terminal has them, ask your agent:

Save these Valet settings in my shell profile.

VALET_CONFIG_DIR keeps this sign-in apart from a valet.dev one. When you sign in, the browser opens your company's sign-in page. If it opens auth.valet.dev instead, the client ID is missing: stop and set it.

Install the skills with npx skills add valetdotdev/skills -g, not the plugin. The plugin's MCP server connects to valet.dev; the skills use the CLI, which follows the settings above.

For a chat app, add https://api.<domain>/mcp as the connector. It works only when your administrator has set up MCP sign-in and the chat app can reach the installation.

Artifacts serve at https://<name>.<org>.<domain>.

Next#

• Skills: share how you do a task with every teammate's coding agent.
• Artifacts: access modes, sharing and updates.
• Apps: tools that need a server or a database.
• Agents: workers that run on their own.
• Data access: connect a tool to real data.