Native macOS · secrets vault
Keys in one place.
Out of your projects.
enveigh keeps your team's secrets in a local, encrypted vault on your Mac, and streams them to your coding agents at runtime, so they never touch a repo, a config file, or disk. Agents use your keys without ever seeing them.

The problem · plaintext keys
Your API keys live in plaintext .env files.
Every repo holds a .env, a config, a line in your shell history: secrets in plaintext, one cat away. The more projects you have, the more places a key hides. enveigh pulls those values into a local, encrypted vault, so your repos hold references, not keys.
The new risk · agents read everything
AI agents read everything, including the key you pasted.
A key in a context window is one tool call away from a log, a transcript, or a paste you don't control. By the time you rotate it, a scraper may already have it. enveigh injects secrets at runtime and redacts them from everything the agent reads back; the model never sees the value.
The audit · rotation & proof
Pass your next security review with rotation and an audit log.
Hardcoded secrets, no rotation, no record of who read what: that's how reviews get failed at midnight. enveigh rotates keys with a roll-back grace window and writes every reveal, render, and agent access to a local audit log, so when the review comes, you have answers.
Why enveigh · the lock
Keys agents can use, but never see.
Your values live in the macOS Keychain and stream to your tools at runtime, reachable by the agents that need them, invisible to the repos, logs, and context windows where keys leak.
Local, encrypted vault
Values live in the macOS Keychain (device-only, unlock-gated). Only non-secret metadata is stored on disk. Nothing syncs to a cloud you don't control.
Use, don't see
Agents run your commands with secrets injected as environment variables, redacted from everything they read back. The model never receives a plaintext key.
Agent-native
An embedded MCP server and CLI let Claude Code, Cursor, and friends run_with_env: a working environment, zero keys in the transcript.
Touch ID gated
Revealing or copying a value takes a fingerprint. The local broker only runs while the vault is unlocked, and every client gets its own scoped token.
Rotation & history
Rotate a key and the old version is retired with a grace window so you can roll back. Expiry reminders surface keys that are going stale.
Audited & honest
Every reveal, render, export, and agent access is written to a local audit log, before the value ever leaves the app.
Watch · 35 seconds
Why enveigh exists
silent · captions on screen
For your agents · CLI + MCP
Built for Claude Code, Cursor, and MCP.
Point an agent at an environment and it gets a working setup to build, test, and deploy, every value injected at runtime and hidden the whole way through.
run_with_env
Run a command with an environment's secrets injected. Output redacted. The preferred path: the agent never holds a value.
list_environments
Discover which environments exist and what they bind: names only, never values.
render_env
When you really need the file, render a full .env: off by default, Touch-ID gated, and audited every time.
Stop pasting keys into terminals.
enveigh is in private beta for macOS: free to download, notarized, and ready to put through its paces.