Secrets and environment

Agents get their configuration through environment variables declared by their skill — API tokens, endpoints, tool credentials. The platform treats these values with a strict rule: secrets are write-only. They are injected into the agent at build/deploy time, stored only in the agent's sealed secret, and can never be read back through the console or the API.

Setting values at create

The configure screen lists every variable the skill declares. Variables flagged as secrets are masked as you type; required ones must be filled before the agent can be created. Values travel server-side only — never in URLs — and secret values are never persisted outside the agent's own sealed secret. Tokens for governed tools and Slack ride the same path.

You can also add your own variables beyond the skill's schema at create time.

Rotating values

Open the agent's Settings tab, Environment variables section. Every variable shows masked (•••• set) — click Edit variables to enter new values:

• Values are write-only: leave a field blank to keep the current value. Enter a value only for what you're rotating.
• Save & restart patches the agent's secret and restarts it. No rebuild — the change is live in seconds.

This is the everyday path for credential rotation, and it stays available even for CI-deployed agents, whose other configuration is locked in the console.

The skill owns the keys

The set of variables — which keys exist, which are required, which are secret — is owned by the agent's skill, not editable from Settings. To add or remove a variable, edit the skill (for AI-generated skills), which rebuilds the agent. During a skill edit, any newly declared secret must be given a value before the rebuild; existing stored values are kept when left blank.