Store credentials centrally and reference them by name in an environment. Keep values out of committed configuration and choose which environments receive each secret.
Store a secret once, then reference its name in environment configuration. Your team can review where a credential is used without putting the value in a repository, prompt, or shared configuration file.
Only environments that name a secret receive its value during setup and agent work. A missing secret fails the session. Once injected, the credential is available to the process and its tools, so grant only the access the task needs.
List stored names and timestamps, replace a value, or delete a secret through the dashboard or API. Stored values are write-only and cannot be retrieved through either interface.
Save tasks, run on demand or with triggers
Run tasks and continue conversations
Reusable repositories, toolchains, and compute
Configure responders for mentions and alerts
Store credentials and select where they are used
Signed session notifications and delivery history
Frontier and open models, bring your own key
Transcripts, live streams, search, cost
Scoped credentials, SOC 2, audit trail
Hard caps per session, agent, and developer