Publish an Agent - Docs menu

Publish an Agent

Publishing turns a draft into a versioned agent that the runtime can serve on a channel.

Drafts and Published Versions

A draft is editable. A published version is the reviewed output of that draft at a specific version. Channels should serve published versions, not unreviewed drafts.

Related concept: Agent Deployment.

Publish Flow

  1. Open Agent Studio.
  2. Open the agent draft.
  3. Review instructions, model route, knowledge, and tools.
  4. Run validation.
  5. Fix any validation errors.
  6. Publish the draft.

What Validation Checks

Validation checks whether the agent can be compiled into a supported runtime bundle. Common issues include:

  • Invalid YAML.
  • Missing required fields.
  • Unsupported tool IDs.
  • Version conflicts.
  • References to unavailable knowledge files.

Version Conflicts

If another version already exists with the same version number, create a new version before publishing. Use small version bumps for small content changes and larger version bumps for behavior changes that reviewers should notice.

Next Step

Deploy the published agent to a channel, then review Eval Center for delivery failures, behavioral eval status, imported suites, and redacted runtime evidence. Eval Center is a review surface for quality signals; it does not replace the channel page as the source of truth for the live serving agent.