Secrets Vault
Keeps API keys behind Touch ID, and gives each project only the keys you approve.
- Role
- Creator
- Team
- Solo
- Status
- In daily use, open source (MIT)
Keeps API keys behind Touch ID, and gives each project only the keys you approve.
Secrets Vault keeps API keys in the Mac's Keychain, behind Touch ID. AI coding agents can list the key names without seeing any value. When a project needs a key, you approve that project and those names, and only they are written to its local .env file.
It runs as a native Mac app with a small local web interface: add, rename, replace, reveal or copy a key, each behind a fresh Touch ID check. Provisioning refuses to run unless the project's .env is ignored by Git, so a key can't be committed by accident. The source is open under the MIT licence.
Mac app
Security
Interface
Add a key once and every new project can ask for it. No more hunting through old .env files, chats or notes.
Your coding agent sees which keys exist and asks for the ones it needs. One Touch ID and you are back to work.
Keys land only in a .env that Git ignores, and values stay masked on screen, so a push or screen share gives nothing away.
Have a question or a project in mind? Send me a message.