Environments & secrets

A workspace separates runtime configuration into environments (for example, production, development, and preview). Each environment decides which secret values apply. Manage environments with oxagen env. See the CLI reference.

EnvironmentsCopy Anchor Link

• Every workspace has exactly one default environment. Promoting another environment swaps the default in one step.
• You cannot delete or deactivate the default environment. Promote a replacement first.
• A sandbox run gets the environment its sandbox runtime names. When the runtime names none, the run gets the workspace's default environment. Agents and people do not choose an environment of their own, so every run on one runtime gets the same secrets.

The secrets vaultCopy Anchor Link

Oxagen models secrets as keys with per-environment overrides:

• A key (for example, DATABASE_URL) lives at the workspace root, with an optional default value.
• Each environment can override the key's value. Unset an override and the key falls back to its default.
• Keys are sensitive by default and envelope-encrypted at rest (KMS). Listing keys returns masked metadata only.
• Reading a plaintext value takes an explicit reveal or export (reveal_secret, export_secrets, or oxagen secret reveal). Each one writes a secret.revealed or secret.exported security event.
• You can paste .env text to bulk-import. Oxagen parses it, previews new keys and overrides, and commits nothing until you confirm.

Oxagen holds the values for connectors (for example, a data connector's own credentials) and for sandbox runs. When a sandbox starts, Oxagen sets the chosen environment's values as its environment variables. It leaves out names that start with OXAGEN_, model provider credential names such as ANTHROPIC_API_KEY, and names the sandbox provider reserves, such as MODAL_ names. No model or provider credential enters a sandbox. A deactivated environment gives a sandbox no values.