Agents forget everything
Every new session starts cold. Hard-won context about your repos, decisions, and preferences evaporates the moment the window closes.
caveauMEM gives Claude Code, Codex, Cowork, and Copilot a memory that survives the session — storage, retrieval, and maintenance across three tiers, sovereign and scoped, with role-based security and an encrypted secret vault.
Every session starts from zero — and the workarounds leak, sprawl, and go ungoverned.
Every new session starts cold. Hard-won context about your repos, decisions, and preferences evaporates the moment the window closes.
Teams burn time and tokens re-explaining architecture, deploy steps, and house rules into prompts that vanish on the next run.
API keys and tokens get pasted inline to "just make it work" — ending up in logs, history, and provider context with no governance.
Once a team shares "company" memory, there is no scoping, no review, and no way to keep confidential work out of the wrong hands.
caveauMEM speaks MCP, so it plugs into Claude Code, Codex, Cowork, and Copilot through a single endpoint — your memory travels with you, host to host.
One memory_bootstrap call at the start of a session loads, in a single shot:
caveauMEM keeps long-term knowledge, short-term scratch, and a replayable timeline distinct, so the right memory is recalled at the right moment.
Durable, searchable knowledge — rules, architecture, decisions, deploy notes. Hybrid dense + BM25 recall with RRF fusion surfaces the right note even when wording drifts.
Fast key/value working memory with a TTL — the agent's short-term notepad for the task at hand. Set it, read it, drop it when the job is done.
An append-only log of what happened and when — a replayable trail of actions and outcomes the agent can recall to stay coherent across long-running work.
Memory is only safe to share when you control who sees what. caveauMEM scopes every note by client, user, and role — and keeps secrets in a vault, never in a prompt.
Every client is a hard boundary. One tenant's corpora, scratch, and episodic memory are never visible to another.
Separate a user's private notes from the shared "company" memory the whole team draws on — without mixing the two.
Owner, editor, tech, and viewer roles map to exactly what each person can read, write, and promote.
Mark corpora internal or confidential. Client-work corpora integrate with caveauCRM so memory follows the account.
Secrets live in an AES-256-GCM vault, fetched by exact key only — never embedded in notes, never searchable, never logged.
New shared memory enters a review queue. A human promotes it before it becomes part of the team's trusted knowledge.
Start free in the caveauAI portal, or book a call to scope a sovereign, scoped memory deployment for your team.
| Hybrid recall | Dense embeddings + BM25 lexical, fused with Reciprocal Rank Fusion (k=60) and a private-scope boost. |
|---|---|
| Graph recall | Traverse links between notes to pull in related context, not just the top-k matches. |
| Context assembler | Token-budgeted assembly packs the most relevant memory into the model's window without overflow. |
| To-do / task tier | Track open work items alongside knowledge, so the agent knows what is still outstanding. |
| Scoping | Per-client (tenant) isolation plus per-user vs shared "company" memory. |
| Role matrix | Owner / editor / tech / viewer roles map to read, write, and promote permissions. |
| Classification | Corpora marked internal or confidential; client-work corpora integrate with caveauCRM. |
| Token scopes | MCP tokens carry memory.read / memory.write / secrets scopes — least privilege per host. |
| Tag taxonomy | repo: / client: / type: / tool: tags drive deterministic, filterable recall. |
| Encryption | Secret vault is AES-256-GCM at rest; exact-key fetch only, never embedded or searchable. |