New in 0.5: AI coding agents can use your secrets without seeing them. From 0.4: quick copy over any app, Touch ID for the command line, importing whole project folders, files kept in sync on disk, and a commit hook that stops leaks.
Secrets for AI agents, not their values
Claude Code, Cursor and Codex run your tests and scripts with the env file loaded, through MCP or the envault command. Values in their output show as [redacted:KEY]; reading one takes your Touch ID. How it works
Quick copy over any app
Press ⌥⌘E anywhere. Search keys, secrets, notes and values, with the ones you copy most at the top. Return copies the value, ⌥Return an export line, ⌘Return KEY=value.
Touch ID for the command line
When EnVault is running, envault asks the app for the key and you approve with Touch ID. Install it from Settings in one click; app updates update it too.
Import your whole projects folder
Point EnVault at ~/Projects. Each folder becomes a project with its .env files; templates like .env.example are skipped. Also imports Doppler, 1Password items, JSON and .env.vault.
.env kept in sync in the project
Link an item to a project folder and EnVault rewrites the file whenever it changes, here, on another Mac or from the CLI. Edits you made on disk are never overwritten without asking.
Secrets stay out of git
envault protect adds a pre-commit hook that stops commits containing API keys, tokens, private keys or a real .env file. Mark a false positive with envault:allow.
An editor that catches mistakes
Line numbers and warnings for duplicate keys, empty or placeholder values and broken lines. See which keys .env.production has that .env.local lacks, and add them in one step.
Every change kept
Each edit is a new revision you can diff and restore, with the Mac that made it. Keys whose value hasn’t changed in 90 days are flagged for rotation.
Variables load when you cd
Link a folder to an env file and the shell hook (zsh, bash or fish) exports its variables when you enter and unsets them when you leave.
Deploy without copy-paste
Push an env file to Vercel, Cloudflare Workers or GitHub Actions secrets with envault deploy, using the vendor CLIs and logins you already have.
Plus, in Pro: env diff, .env.example generator, secret scan, JWT decoder, UUID and password generators.