Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.guild.ai/llms.txt

Use this file to discover all available pages before exploring further.

Publishing makes an agent version available for installation. Today, the CLI docs describe publishing as making an agent available to your organization.

Publish with `guild agent save`

You can save, validate, and publish in one command:
guild agent save --message "Ready to ship" --wait --publish

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:
guild agent publish
To wait for validation before publishing:
guild agent publish --wait

Visibility and who can install

The CLI docs state that `—publish` makes the agent available to your organization.

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)
If validation fails, check the latest version and save again:
guild agent versions --limit 1
guild agent save --message "Fix validation error" --wait

What appears in the Agent Hub listing

The docs do not currently specify which fields appear in the Hub listing and where each one comes from in the agent source.

Update a published agent

To update an agent, save a new version and publish it:
guild agent save --message "Update behavior" --wait --publish
To inspect status and version history:
guild agent get
guild agent versions

Unpublish

To unpublish the latest published version:
guild agent unpublish

View your published agent in the UI

Open app.guild.ai, go to Agents, then click Add agent to browse the Agent Hub.