Skip to main content
Every time you save an agent, Guild creates a new version. Versions let you iterate on agent code while keeping previous versions available.

​
Version lifecycle

​
Version states

​
Tool and dependency validation

When you save an agent with guild agent save, Guild validates the tools and dependencies declared in the build before persisting the version. If a declared dependency is broken or violates visibility rules, Guild rejects the build with a 400 BadRequest error and lists the specific validation failures. Guild rejects the build when your agent depends on:
  • A private sub-agent or integration owned by another account.
  • A private sub-agent or integration owned by the same account when the agent itself is public.
  • A sub-agent that has been archived.
Resolve the reported dependencies and save again to build a valid version.

​
Testing before publishing

Use guild agent test to create a temporary version for testing without saving:
Ephemeral versions are created automatically when testing from a local agent directory and don’t appear in your version history.
Ephemeral versions include only files tracked by Git. Files that are already committed or staged with git add are uploaded. New untracked files are ignored until you stage them with git add. Modified tracked files still upload their working-tree content, so you can test uncommitted changes to existing files without committing them first.

​
Listing versions

​
Publishing

Publishing makes a validated version available to your organization. Other team members can install published agents into their workspaces.