Copy it everywhere.
Keys in .env files, shell history and config. Anything that can read your disk can read them, and now that includes your agents.
Keep holds your keys, tokens and passwords in one encrypted vault on your machine, and lets your tools use them without ever handing them over.
The question used to be where a secret is stored. Now it's who gets to use it, and for what.
Keys in .env files, shell history and config. Anything that can read your disk can read them, and now that includes your agents.
Better storage, same hand-off. Once a value is pasted or exported, it's out of reach of any rule you set.
Tools ask Keep to sign, authenticate or connect. Keep checks who is asking, asks you, and does the work. The secret stays put.
A coding agent can read every file you can. Keep moves secrets out of files and into one local process that knows who is asking, asks you when it matters, and records every answer.
ssh, git, AWS and the rest work as they do today. They just ask Keep instead of reading a file.
credential_process, Docker and kubectl plugins.One place decides. Every use of a secret goes through the same checks, the same prompt and the same log.When something wants a secret, Keep shows you what it could verify about the caller, separately from what the caller merely says about itself. You decide once, until the vault locks, or for good.
To push to github.com/acme/web
More automation should mean less exposure, not more.
A token in a file is a token for every process, script and agent that can open that file. You find out what read it after the fact, if at all.
Keep signs, authenticates or connects on the caller's behalf. An agent can call an API with your token and still never see it.
keep http takes the same options as curl. Keep adds the key, sends the request, and hands back only the response.
export MOCK_KEY=mpk_…
curl -H "Authorization: Bearer $MOCK_KEY" \
-F file=@site.zip \
https://mock.soundheart.io/api/mocksAnything that runs the script, or reads its environment, can read the key, and a -v prints it.
keep http --secret global/mock \
-F file=@site.zip \
https://mock.soundheart.io/api/mocksUploads, headers and JSON bodies work as before. If the server echoes the key back, Keep removes it from the response.
keep item hosts global/mock --only-host mock.soundheart.ioPin a key to its API. Requests anywhere else are refused before you are even asked, so a script or agent steered by a poisoned README still can't send it somewhere else.keep doctor checks each one really goes through Keep, and flags plaintext copies left behind.
A built-in SSH agent. Private keys stay in the vault, can be limited to certain hosts and can refuse forwarding.
HTTPS credentials through the credential helper, and SSH commit signing.
Values become keep://app/db. Drop-in loaders for Node, Python and Rust.
Short-lived credentials via credential_process, plus EKS and RDS tokens.
A registry credential helper and a kubectl credential plugin.
keep db exec -- psql hands the password to that one command and nothing else.
Agents call APIs through Keep. Each destination host needs your approval; the token never reaches the agent.
Sign with Keep's keys from any PKCS#11 program, including ssh -I.
keep http replaces curl -H "Authorization: …": same options, uploads included, and the key never enters the script.
Keep is local-first, open in format and conservative in its cryptography. Each of these is covered by Keep's test suite.
One encrypted file on your machine. No account, no server, no sync you didn't ask for.
Moving a vault or sharing an item uses hybrid X25519 + ML-KEM-1024, so a recorded bundle stays safe later.
AES-256-GCM-SIV and Argon2id, fully documented. An independent reader opens the vault from the spec alone.
Optionally bind unlocking to the Secure Enclave with Touch ID, or to a TPM on Linux. Your passphrase still works.
When you step away, the screen locks, the machine sleeps or another user logs in. An older copy of the vault is refused.
Every decision and every use goes into a hash-chained audit log. Edit it and keep audit verify notices.
Keep is in private preview on macOS, Linux and Windows. If you run agents on real code with real credentials, we'd like to hear from you.