secrets

# Secrets Store credentials in your OS keychain and inject them into agent runs. Nothing touches disk in plaintext — not even the bundle metadata. ## Platform support | Platform | Backend | Install | |----------|---------|---------| | macOS | Keychain | Built-in | | Linux (desktop) | GNOME Keyring (libsecret) | `sudo apt install libsecret-tools` | | Linux (headless/server) | Use `env:` refs | See below | | Windows | Credential Manager (primary) + encrypted-file fallback | Built-in | **Desktop Linux:** GNOME Keyring (or another Secret Service provider) must be running. Most desktop environments start it automatically. **Headless Windows (service accounts, SSH with no interactive logon):** Credential Manager needs a logon session; without one it fails with `ERROR_NO_SUCH_LOGON_SESSION` (1312) and secrets transparently route to the AES-256-GCM encrypted-file store. Set `AGENTS_SECRETS_PASSPHRASE` so that store has an off-disk key — otherwise a machine-local key is provisioned next to the ciphertext. **Headless Linux (SSH, CI, containers):** No keyring daemon available. Use `env:` refs to pass secrets via environment: ```bash # Create bundle with env refs agents secrets create prod agents secrets add prod DB_PASSWORD --env DB_PASSWORD # Pass at runtime DB_PASSWORD=xxx agents run claude "..." --secrets prod ``` Vault providers (1Password, AWS Secrets Manager, HashiCorp Vault) are planned for headless environments. ## Why not just use .zshrc or 1Password? **Environment v...