An agent learns something reusable.
Claude Code fixes a test failure and proposes the lesson as a candidate, not as trusted memory.
Vault Agent Memory Demo
This visual demo shows why Vault is not just a RAG database: agents can propose memory, but shared knowledge becomes trustworthy only after gates, review, source evidence, rollback, and audit.
The point is not that Vault can store text. The point is that shared agent memory has a lifecycle.
Claude Code fixes a test failure and proposes the lesson as a candidate, not as trusted memory.
Privacy, duplicate, metadata, quality, and source checks decide whether it is safe enough to proceed.
Low-risk sourced lessons can be kept automatically. High-impact or uncertain memory waits for the daily report.
Codex or Hermes searches the shared vault, then reads a bounded source range before citing it.
If the project changes, the memory can be deprecated, replaced, audited, or restored from backup.
The user reviews a short report instead of learning every CLI command or reading every raw chat log.
This is the wedge for Codex, Claude Code, Hermes, OpenClaw, Coze, and n8n: one governed memory layer, many adapters.
Notes remain readable, but agent memory gets source, review, permission, and rollback boundaries.
RAG reads. Vault also governs what agents write, trust, forget, and share.
The default path is local-first. Supabase, Gateway, and future remote servers are adapters.
pip install "vault-for-llm[mcp]" vault quickstart vault demo agent-governance --json