Valet|Docs
Sign up

Dashboard: Artifacts

The dashboard at dashboard.valet.dev is where your team works with everything it has published. Signing in lands you on Sites: a wall of every artifact your organization has published, newest deploy first.

Each card is a live preview of the real page, with the artifact's name and description, who published it — a person or an agent — a lock when it is not public, and how recently it deployed. A filter box narrows the wall by name or author.

Publishing an artifact

Publishing happens from your agent, and the Sites page hands you the prompt to do it. At the top of the page, Publish a site shows a copy button. Paste what it copies into Claude Code, Codex, or Cursor from the folder you want published.

The instructions route themselves. Your coding agent installs the Valet plugin where its harness has one and the skills where it does not, signs in, deploys, and prints the URL. The new artifact appears on this page, private to your organization by default. Nothing needs to be uploaded through the browser.

An agent with no terminal cannot run any of that. The same panel offers Valet's MCP server for those — see Connect Your Agent.

An artifact's page

Selecting a card opens the artifact. The header shows its status — Configuring, Not deployed, or Running vN — and there are two tabs:

  • Content — the live artifact, embedded. Private and password artifacts preview signed in as you, and a first-party link opens the page in its own tab.
  • Sharing — the artifact's addresses and who may open them.

Who can view

The Sharing tab offers three access modes:

  • Private — only members of your organization, after signing in. New artifacts are private.
  • Password — org members, or anyone who enters the password. Meant for people outside the company who will never have a Valet account. The dashboard reveals, edits, and copies the current password.
  • Public — anyone with the address.

Switching modes takes effect immediately and signs current visitors out. To let a teammate in permanently, invite them to the organization from Team.

Addresses

The Sharing tab lists every address the artifact answers on, with the canonical one marked Primary. An artifact's first address is minted the first time it deploys, and takes the shape <artifact>.<org>.valet.run.

Claiming an anonymous artifact

An artifact published without an account is public and temporary — it is removed 36 hours after it was created. The claim link printed when it was published opens a dashboard page that asks one question: which organization the artifact should live in, including creating a new one on the spot. The name is editable there, with a preview of the final URL. Signing up from a claim link claims the artifact automatically when you return.

Updating an artifact

Publishing again from the same folder replaces the content at the same address. Ask your coding agent to fetch the deployed files if you no longer have them locally — it can edit and redeploy from anywhere. An agent you built can do the same on a schedule, so a dashboard refreshes itself.

Taking an artifact down

The artifact menu's Destroy site asks you to type the artifact's name to confirm. It stops serving immediately and its content is deleted; its address is never reissued to a future artifact.