Publish to a public URL

Publishing puts a deployed copy of an app or markdown artifact on a public URL: a web address that anyone can open without an AgentGrid.io account. Sharing an artifact link does not do that.

Before you publish

You need publish permission in the artifact's workspace. A custom domain also requires a paid plan that includes custom domains. Publishing is a privacy decision: treat the resulting URL as publicly discoverable.

Publish and update in the app

1. Open the current artifact and choose its publish control.
2. Review the public state, which shows whether the artifact is available on the web, and confirm the first publish.
3. Open the returned public URL to verify it.
4. After later artifact edits, Unpublished changes means the public deployment still shows the last published version. Publish the update when you want those edits live.
5. To take the page offline, choose Unpublish. Unpublishing removes public access without deleting the artifact or its History.

Apps and markdown artifacts can both be published. Mermaid in markdown renders on published pages.

Agent route

A connected agent with the publish capability, meaning permission to deploy the artifact publicly, can use anima publish <sessionId> and anima unpublish <sessionId>. Here, <sessionId> is the artifact's unique ID. Agents must never publish or unpublish without an explicit human request. After either command, verify the public URL or its removal.

Custom domains

Custom domains are web addresses that you own. They are available on paid plans that include this feature. Start domain setup from the artifact's publishing controls, enter the domain, and add the DNS records AgentGrid.io provides. Custom-domain verification checks that those records prove you control the domain. Wait for that check to pass. Use Plans and usage and the live pricing page to see which plans include custom domains. Do not remove a working record until the replacement is verified.

Errors and recovery

Access or plan denial requires human action and should not be retried unchanged. For failed domain verification, compare the displayed DNS values with your provider, allow for DNS propagation, and retry verification. If the artifact changed during publishing, inspect the public result and publish the intended current version again.

Related: Share an artifact · Version history

Questions and answers

Who can open a published URL? Anyone can open it without an AgentGrid.io account, so treat it as publicly discoverable.

Do saved edits update the public page automatically? No. Unpublished changes means the public URL still shows the last published version; publish again when the new version should go live.

Does Unpublish delete the artifact? No. It removes public access while preserving the artifact and History.

How do I verify a custom domain? Install the exact DNS records shown, wait for propagation, and confirm that AgentGrid.io’s verification passes before removing any working record.

Direct answer

Publishing deploys the current app or markdown artifact to a public URL, which is a web address anyone can open without an account. Sharing preserves access controls; publishing makes a deployment public.

Consent and capability gate

Never publish, republish, or unpublish without an explicit human request. To unpublish is to remove the public deployment while keeping the artifact. Require the publish capability, or permission to deploy publicly, in the artifact's workspace. A suggestion to publish is not consent.

CLI operations

CLI means command-line interface: a tool used by typing commands in a terminal. In these commands, <sessionId> is the artifact's unique ID.

• anima publish <sessionId>
• anima unpublish <sessionId>

After publish, open or otherwise verify the returned public URL. After unpublish, verify that public access is removed while the artifact and History remain. A successful command response alone is not sufficient verification.

Deployment state

• First publish creates the public deployment.
• Unpublished changes means the saved artifact is newer than the version currently available at the public URL.
• Republish intentionally to update the public page.
• Unpublish removes public access but does not delete the artifact.
• Both app and markdown artifacts can be published; published markdown supports Mermaid rendering.
• Treat public URLs as discoverable.

Human-only custom-domain setup

Custom domains are web addresses owned by the human and require a paid plan that includes custom domains. Ask the human to begin in publishing controls, enter the domain, and install the exact DNS records shown. Custom-domain verification checks those records to prove control of the domain. Wait for that check to pass. Do not invent DNS values. Check Plans and usage and pricing.

Failure handling

Workspace denial, missing publish capability, and plan denial are terminal failures: retrying cannot help until a human changes access or plan state. For DNS verification, have the human compare displayed records, wait for propagation, and retry verification. If the artifact changed during deployment, verify the public output and publish the intended current revision again only with human confirmation.

Related: Share · Version history

Questions and answers

Which identifier do CLI publish operations require? Use the artifact’s unique <sessionId> with anima publish or anima unpublish.

What consent is required? An explicit human request is mandatory for publishing, republishing, or unpublishing; a suggestion is not consent.

How is success verified? After publish, open the public URL. After unpublish, confirm public access is gone while the artifact and History remain.

Which failures are terminal? Workspace denial, missing publish capability, and plan denial require human action and should not be retried unchanged.