Skip to main content
Copy page
Version: Next

Environment

An Environment is an isolated space where your agents run and resources are deployed. Typical examples include development, staging, and production. Every agent deployment, gateway registration, and MCP proxy endpoint in Agent Manager is scoped to one or more environments.

Built on OpenChoreo's Environment Abstraction​

Agent Manager's environments are OpenChoreo Environments. OpenChoreo defines an Environment as representing "a stage in the software delivery lifecycle, such as development, staging, or production," providing the context for deploying and running applications — the policies, configurations, and constraints that apply there. Each environment maps to a distinct deployment target (an OpenChoreo Data Plane).

What's Scoped Per Environment​

Because agents, gateways, and proxies are all deployed per environment, most of what you configure in Agent Manager varies by environment rather than being set once globally:

  • Agent deployments — a given agent version is deployed independently to each environment it's promoted to.
  • AgentID — every environment provisions its own dedicated identity for each agent that runs in it; see Agent ID.
  • Gateway artifacts — an LLM Service Provider or MCP Proxy deploys one gateway artifact per environment it's configured for, to that environment's active Gateway.
  • Identity providers — the token issuers each environment's gateway trusts. A token accepted in development is not automatically accepted in production.

Relationship to Deployment Pipelines​

Environments don't stand alone — a Deployment Pipeline defines the order agents are allowed to move through a set of environments (for example, requiring a dev deployment before staging, and staging before production).