Skip to main content
Environment is where you store the secrets your agents and integrations need.

​
What gets stored here

Typical secrets include:
  • GITHUB_TOKEN
  • RESEND_API_KEY
  • DATABASE_URL
  • PRIVY_APP_ID
  • PRIVY_APP_SECRET
  • Provider tokens for X, Twilio, Cloudflare, Google Workspace, Replicate, and others

​
Secret access modes

​
Global

A global secret is automatically available to all of your instances.

​
Instance specific

An instance specific secret stays locked until you grant that instance access. Use this when different agents should use different accounts, repositories, or environments.

​
Important behavior

  • Secret values are encrypted at rest.
  • You only see the full value once when you create it.
  • Installing a skill does not create or grant its secrets.
  • The matching secret still needs to exist and be accessible.

​
Common skill requirements

Skill or workflowTypical secret names
GitHubGITHUB_TOKEN
Vercel deploysVERCEL_TOKEN, GITHUB_TOKEN
ResendRESEND_API_KEY
PrivyPRIVY_APP_ID, PRIVY_APP_SECRET
PostgreSQLDATABASE_URL
XX API secrets used by your X skill setup
TwilioTwilio account secrets used by your SMS skill setup
CloudflareCloudflare API token

​
How managed skills use secrets

Managed skills fetch secrets at runtime. That means:
  • values are not hardcoded into the skill
  • rotated secrets are picked up on the next use
  • cron jobs inside an instance should also fetch secrets at runtime
  1. Add the secret in Environment.
  2. Decide whether it should be global or instance specific.
  3. If it is instance specific, grant access to the right instance.
  4. Ask the manager or the agent to use the skill.