What Latchkey does today for developers and AI agents — without cloud vaults.
Secrets are sealed with libsodium secretbox. The master key prefers your OS keychain (keytar). Passphrase mode uses Argon2id. Plaintext never leaves the machine for storage.
CLI, daemon, and MCP flows present approve or deny before injection. Hardened policy on Business can require approval on every access.
.latchkey.toml lists the env names a repo may request. Anything else is refused — even if it exists in the vault.
Append-only JSONL under ~/.latchkey records action, name, and context. Values are never logged.
Offline heuristics over a path or paste. Matches are redacted in the terminal. Guidance walks rotation without uploading the tree.
Team and Business plans include the /app/team surface for shared billing context. Sharing & invites remain Coming soon until shipped.