Deploy a Claude artifact for your whole team, from your AI agent
Does your Claude artifact save your whole team time? Connected to while over MCP, your agent deploys it, and your colleagues open it without a Claude account.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 2, 2026.
Prerequisites
- A Claude artifact, saved as index.html, with no other file in its folder.
- An AI agent that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.
Step 1: Give your agent these instructions
Open your agent in your artifact’s folder, and paste these instructions into it:
Connect to while with my account (while.sh/agents), then deploy my app.Without an account, your agent deploys your artifact as a trial, in one request. To keep it, open the link it gives you and create your account.
With your account, your agent adds while’s MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn’t open, type /mcp, choose while, then Authenticate. On that page, choose your app, or “A new app”, then click Authorize.
Step 2: Open your artifact
Your agent gives you your artifact’s address, for example https://planning-equipe.while.cloud, over HTTPS.
What your agent does
It writes while.yaml next to your file:
apiVersion: while/v1
project: planning-equipe
services:
- name: web
type: static
root: .Your artifact is served as it is, over HTTPS, with an HTTP cache.
Restrict your artifact to your colleagues
You, to your agent: Restrict the artifact to people in the company.
Your agent adds two lines to the service:
access: internal
email_domains: [acme.com]Once your Google Workspace or Microsoft 365 is linked to while, on the Pro plan, your colleagues open the artifact with their usual account, with no sign-in page to write.
Share with a customer, protected by a password
You, to your agent: Open the artifact to our customer, with a password.
Your agent makes the app private. Then, on the app’s page in while, you create a link that lasts 1, 7 or 30 days, with a password your agent will never see.
Keep the team’s data
You, to your agent: Keep the team’s answers in a database.
Your agent adds a PostgreSQL database and a small API next to the page. Everyone’s data stays there from one visit to the next.
Move to your own domain
You, to your agent: Put the artifact on planning.acme.com.
Your agent declares the domain, you add the DNS records it gives you, and the HTTPS certificate follows.
Go back to the previous version
You, to your agent: Go back to the previous version.
In the 30 minutes after a deployment, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your agent reads what broke in while’s logs, fixes it and deploys again.
In the docs: Static site, Internal access, Custom domain and Versions and rollback.
Next steps
Sources
- Claude, help on artifacts (HTML export, the code), accessed November 2, 2026
- Claude, help on sharing artifacts, accessed November 2, 2026