Direct answer
Publishing deploys an artifact's current version to a public URL that anyone on the internet can open without an account. Publishing is different from sharing: sharing grants team members access to the artifact, while publishing exposes a deployed version on the open web.
Availability
There is no publish control in the app today. The artifact view has Export and Share, but publishing and unpublishing currently require a connected AI.
A human can ask the connected assistant:
Publish this AgentGrid.io artifact to a public URL.
To remove the live page:
Take that published page offline again.
Mandatory agent consent rule
Never publish unless the human explicitly asked. Making work visible within the human's team is not permission to expose it publicly. Sharing an artifact URL and publishing to the internet are different decisions.
If publishing may help, offer it as a follow-up question. Do not publish automatically.
Publish, update, and recovery semantics
- Publishing deploys the current version.
- Later artifact changes do not reach the public URL until the artifact is published again. The live page and current artifact can therefore differ.
- Unpublishing clears only the live URL. It does not delete the artifact, its content, or its history.
- Publishing again reuses the same address.
- A public URL requires no account and must be treated as discoverable by search engines.
- The team-only artifact link is not the public URL.
Document limitation
Publishing deploys a web page. For a document, share it with the team or export it as PDF.
Coming soon
- An in-app publish flow that shows which changes landed since the last publish.
- Publishing to a human-owned domain instead of the default domain.