Managing Deployments

Once a page is live, you can check its status, push updates, list all your deploys, or tear it down — all through Claude.

Checking Status

"What's the status of my project deployment?"

Claude calls get_status with the deployment ID. The response includes:

Field	Description
URL	The live URL ({slug}.based.page)
Status	Whether the deployment is active
Storage	Storage type (single HTML or multi-file)
SPA mode	Whether 404→index.html fallback is enabled
Created at	When the deployment was first created
Updated at	When the content was last updated

Listing All Deployments

"Show me all my active deployments"

Claude calls list_deploys and returns a summary of every active deployment with its URL, slug, title, and last update time.

Updating a Deployment

"Update my project page — change the headline to 'Now in Public Beta' and swap the button color to green"

Claude calls update with the deployment ID and the new HTML or files. Changes go live immediately.

Key behaviors:

• Same URL — the slug and subdomain don't change
• Live immediately — updates apply as soon as update returns
• Supports multi-file — pass a new files array to replace all files

Use this for iterating on a live page:

"Add a contact section to my landing page"

"Redesign the page with a darker theme"

"Update the hero text across all pages"

Tearing Down a Deployment

"Take down my old project page"

Claude calls teardown with the deployment ID. This uses a two-step confirmation flow:

1. Claude first calls teardown without confirming, which returns a preview showing the deployment URL and title.
2. After you agree, Claude calls teardown again with confirm: true to proceed.

When a deployment is torn down:

• The URL immediately returns a 404
• The deployment is marked as deleted
• The slug becomes available for reuse

Teardown is permanent

There is no undo. If you might want to bring the page back, consider using update to replace the content with a "closed" or "coming soon" message instead.

Notes

• The free plan allows 5 active deployments at a time. Tear down unused deployments to free up slots.
• You can update a deployment from single-file HTML to multi-file (or vice versa) by passing the appropriate parameter.
• Use list_deploys to find deployment IDs when you don't remember them.