Secrets for unsupervised agents (1Password op)

Tool roles, alternatives, selection tradeoffs, and compatibility caveats.

Tool roles, alternatives, selection tradeoffs, and compatibility caveats.

Secrets for unsupervised agents (1Password op)

John uses: the 1Password op CLI (commercial). AGENDA directive #10: agents are safe to run unsupervised if secrets live in a vault and get injected per-command (op run / op read) instead of sitting in .env files any agent can read or leak.

Alternative What it is How it differs License
Bitwarden CLI (bw) CLI for the Bitwarden password manager (open clients, optional self-host via vaultwarden) Open-source clients and self-hosting; scripting ergonomics rougher than op run NOASSERTION (GPL/Bitwarden License mix)
Infisical Open-source platform for secrets, certificates, and privileged access; CLI injects env vars Team/infra-grade secret management with `infisical run` (the closest op-run analog); self-hostable NOASSERTION (MIT + enterprise dirs)
Doppler CLI Official CLI for Doppler secrets/config: `doppler run -- cmd` injects secrets as env vars SaaS-hosted; the smoothest run-with-secrets DX after op Apache-2.0
sops Encrypt secrets inside files in your repo (age/KMS/PGP), decrypt on use Secrets live encrypted next to code — no vault service at all MPL-2.0
pass + age The UNIX password store (GPG) and the modern simple file-encryption tool Fully local/offline, scriptable, zero SaaS; you assemble the workflow yourself GPL-2.0 (pass) / BSD-3-Clause (age)

Pick this if…

  • Infisical — you want the closest open op run experience and can self-host.
  • Doppler — you want the smoothest SaaS run-with-secrets DX.
  • Bitwarden — you already use it as a password manager; the CLI comes along.
  • sops (+age) — you want secrets versioned encrypted next to code, no vault service.
  • pass + age — you want fully local, scriptable, zero-SaaS.

Source references