Skip to content
Browse the docs

Secrets

Store API keys, tokens, and kubeconfigs as write-only secrets in Nested, keep them private or share them with your team, and attach them to agents.

Updated 1 min readView as MarkdownOpen in Nested

Packs and coding agents need credentials. Secrets keep them in one place, so you never paste keys into chat and can reuse them on the next deploy. Values are write-only: Nested never shows them again after you save.

Before you start#

  • Open Settings → Secrets.

Steps#

  1. Select New secret.
  2. Enter a Secret name (for example GITHUB_TOKEN) and the Secret value. Line breaks are kept, so you can paste a token, a kubeconfig, or a certificate. Use Show value to check what you typed.
  3. Optional: add a Description.
  4. Set Who can use it?: Only me, or Everyone to let anyone in the team attach it.
  5. Select Save secret.
  6. Attach the secret to an agent — in the deploy wizard’s Secrets step, or in the agent’s settings → Secrets with Attach secret. The secret is injected under the environment variable you choose, not under its own name.

To change a value, select Edit and enter a New value; leave it empty to keep the current value. Delete removes the secret, and agents using it lose the value.

Example#

Create SEARCH_API as Only me, then attach it as SEARCH_API_KEY when you deploy a research agent whose pack asks for that variable.

Questions

Can I see a secret’s value after saving it?
No. Secret values are write-only. To change one, edit the secret and enter a new value.
Where are secrets stored?
On your team’s cluster, as part of your Nested installation. See Security model.