# Set an API key

API keys (and every other credential) live in the **encrypted secrets vault** — an AES-256-GCM table in the local SQLite database. Values are written once and never shown back; the UI only ever reports whether a key is **set** or **unset**.

## Fastest way: Cmd+K

1. Press **⌘K** (or ⌘Space) anywhere to open smart search.
2. Type what you want, e.g. `api key`, `anthropic`, `resend`, `github`, `supabase`.
3. Pick the **Set …** result. A small modal opens with one field.
4. Paste the value and press **Save**.

That's it. The value is encrypted and stored immediately. The modal shows the current status (set / unset) and links to the full Settings page.

## Where values show up afterwards

The Settings pages are the full view:

- **Settings → Tools & secrets** — count and status of stored secrets.
- **Settings → Connectors** — per-tool credential readiness (ready / missing).

Both surfaces show **names and status only** — never the secret value. That is a hard security rule, not a limitation.

## Common keys

- `ANTHROPIC_API_KEY` — see [Set the Anthropic API key](/help/set-anthropic-key)
- `RESEND_API_KEY` — see [Set the Resend API key](/help/set-resend-key)
- `GITHUB_TOKEN` — see [Set a GitHub token](/help/set-github-token)
- `SUPABASE_URL` / `SUPABASE_SERVICE_ROLE_KEY` — see [Connect Supabase](/help/connect-supabase)

More on storage and encryption: [Secrets vault overview](/help/secrets-vault-overview).
