Skip to content

Agent deployment

An agent deployment is the record that a specific version of an agent is the current release in a specific environment.

When you ship a new version of your agent to production, you update the agent deployment for that environment to point to the new version. The deployment record says: “in this environment, this version is what’s running.” That makes it explicit and reviewable — anyone inspecting the platform can see exactly which version is live in each environment at any given time, and when it was last updated. Environments can carry different versions simultaneously, so staging and production can diverge deliberately rather than by accident.

An agent deployment sits at the intersection of three concepts: the agent it belongs to, the version it points to, and the environment it covers. There is at most one active deployment per agent per environment. Updating a deployment — deploying a newer version — is tracked with a timestamp, so the history of what ran where is always available.

Agent deployments are distinct from deployment tokens. A deployment token is a credential scoped to one agent in one environment; it carries the agent identity at runtime so your SDK does not need to supply it separately. The token and the deployment record are related — a deployment token is issued for a specific deployment — but the token is a secret used for authentication, while the deployment record is the platform’s statement of which version is current.

  • The deployment snapshot on the Agent page — the current version deployed to each environment and controls to update it.
  • Agent › Deployments tab — deployment-scoped tokens for each agent deployment.
  • Agent — agent deployments belong to an agent; each agent accumulates deployments across its environments.
  • Environment — each deployment covers one environment; environments can be on different versions at the same time.
  • API token — deployment tokens are scoped to one agent deployment and carry its identity at runtime.