AgentVault
in development开发中The credential vault for agents. Secrets that never reach the transcript.面向智能体的凭证保险库。绝不进入对话记录的密钥。
Agents read .env in the clear and the keys end up in logs and provider transcripts. AgentVault closes that hole: one encrypted vault, one master password, and secrets delivered as environment variables at the exact moment a command runs. Offline-first, single binary, optional zero-knowledge sync.智能体会以明文读取 .env,密钥最终落入日志与供应商的对话记录中。AgentVault 堵住这个漏洞:一个加密保险库、一个主密码,密钥在命令运行的精确时刻作为环境变量交付。离线优先、单一二进制、可选的零知识同步。
- Runtime injection.运行时注入。 Secrets enter the process as env vars — never printed, never logged, revealed only on explicit request and audited when they are.密钥以环境变量进入进程——从不打印、从不记录,仅在显式请求时显露,并在显露时被审计。
- Boring cryptography.无趣的密码学。 Argon2id for key derivation, XChaCha20-Poly1305 for everything else. Standard primitives only — no custom crypto to regret.Argon2id 用于密钥派生,XChaCha20-Poly1305 用于其余一切。只用标准原语——没有日后会后悔的自定义密码。
- Rotation without re-encryption.无需重新加密的轮换。 Envelope keys: changing the master password rewraps one key, the vault body is never touched.信封密钥:更换主密码只需重新包装一把密钥,保险库本体从不被触碰。
- Tamper-evident.防篡改可证。 The audit log is an HMAC chain —
doctorverifies it or tells you where it broke.审计日志是一条 HMAC 链——doctor会验证它,或告诉你它在哪里断裂。 - Recovery is a real plan.恢复是真正的预案。 A 24-word BIP-39 recovery key opens the vault if the password is gone. Losing both is the only failure mode.若主密码遗失,一把 24 词 BIP-39 恢复密钥可开启保险库。唯一会失败的情形,是两把都丢。