Publish with `guild agent save`
You can save, validate, and publish in one command:Key flags
- `—message`: Sets the version message for this save.
- `—wait`: Blocks until validation passes.
- `—publish`: Publishes after a successful save (and after validation if you also pass `—wait`).
Publish separately
If you already saved a draft version, you can publish later:Visibility and who can install
Agents have three visibility states:- Draft: no published version. The agent is not available for installation.
- Team-installable: published with visibility restricted to your organization (
is_public=false). Organization members can find and install the agent from the organization Browse tab and category pages. - On-Hub: published and listed on the public Agent Hub (
is_public=true). Anyone can find the agent on the Agent Hub. Organization members also see it in the organization Browse tab and category pages.
guild agent save --publish or guild agent publish makes the agent Team-installable by default.
What validation runs during `—wait`
`—wait` blocks until validation passes. The docs do not currently enumerate the full set of validation checks. Common failure modes called out in troubleshooting:- TypeScript errors in `agent.ts`
- Saving without being inside an agent directory (one with a `guild.json` file)