Skip to main content
An environment is a named slot in a project, such as prod, staging, or canary, that the project’s prompts and skills publish to. Every project starts with two: prod (Production) and staging (Staging).
Today a prompt or skill has one label, latest, which follows its newest version. Rendering a chat prompt and syncing a skill serve latest; the environment does not change which version is served. See Versions.

Managing environments in the dashboard

Open Settings at the bottom of the sidebar, then Environments under Project. The page lists the project’s environments in order; drag a row to reorder them. New environment asks for:
  • Name — the display name.
  • Slug — the lowercase, hyphenated identifier, such as staging. The slug is fixed once the environment is created.
  • Description — optional, shown in the environment list.
  • Color — a color that marks the environment in the dashboard.
Configure on a row opens the environment’s settings, where you can change its display name, color, and description, and turn on Default publish target: the first publish of a new prompt targets the default environment. The Context group shows the environment’s ID. Creating, configuring, and reordering environments needs the project:manage_environments permission, which owners and admins hold. Anyone who can read the project can view its environments.

Listing environments from the CLI

to11 environment list prints a project’s environments that are not archived:
See to11 environment list.

Managing environments from the SDKs

Both SDKs expose a project’s environments as projectEnvironments (TypeScript) and project_environments (Python), with list, get, create, update, archive, and restore. Archiving an environment hides it from the default list; restoring brings it back. See Prompt management in the TypeScript SDK reference.

Next steps

Projects

Create and manage projects.

Versions

How a prompt version is published.