Environments
Separate staging from production so agent config and deployments are isolated per stage.
An environment is a named stage (for example staging and production) that isolates which prompts, skills, and resources are active — so you can validate changes in one stage before they reach real users in another.
The four environments
Every workspace has the same four environments, provided by the platform when the workspace is created. You cannot add, rename or delete them.
| Environment | Name | Used for |
|---|---|---|
| Draft | draft | Private authoring sandbox, not deployed |
| Development | dev | Team development, with mocks |
| Staging | stg | Integration testing |
| Production | prod | Live traffic |
If a workspace shows no environments, its setup did not complete — contact your platform administrator.
See what is active in an environment
- In the sidebar, open Settings and choose Environments under Release.
- Click an environment.
- Review the Skills, Prompts, and Resources active in it.
Tip: Confirm behaviour in stg before you promote a version to prod.
Related
- Deploy an agent — promote a version to an environment.
- Safe rollouts — environments and change discipline.