Environment
Development, staging and production of one application, configured independently.
An environment is where runtime configuration lives. Two environments of the same application share nothing operational: separate provider keys, separate limits, separate trusted issuers, separate service accounts, separate tool bindings. A change in development cannot reach production.
Kinds
An environment is development, staging or production. Production is marked throughout the console so destructive actions stay visible, and a production environment shows a red indicator in the scope switcher and the top bar.
Limits and kill switches
Each environment carries its own ceiling on concurrent runs, run duration, tokens per run, and audit retention. It also carries three switches that stop work immediately without deleting anything.
| Switch | Effect |
|---|---|
| Disable new runs | Existing runs finish; nothing new starts. |
| Disable token exchange | Blocks delegated identity from being issued at all. |
| Disable tool execution | Agents may reason, but may not act on your systems. |
Allowed origins
Browser requests are refused unless they come from an origin listed on the environment. This is a comma-separated allowlist, and it is checked on every mutation.