Browse / Professional & finance / openclaw-mem
openclaw-mem
phenomenoner
The AI agent memory layer you can audit — local-first memory governance for AI agents: citations, trust policies, trace receipts, rollback.
Open phenomenoner/openclaw-mem → Does not match the four rules.
agent-memoryai-agentsai-memorycontext-engineeringllmllmopslocal-firstlong-term-memorymemory-governancememory-systemsobservabilityopenclaw
Works with any agent
ships AGENTS.md, the cross-tool instruction file.
In its own words
SQLite, sidecar-first, OpenClaw plugin.
The AI agent memory layer you can audit.
Local-first memory governance for AI agents — every context item cited, every exclusion explained, every mutation reversible.
Most AI agent memory systems compete on recall — remember more, retrieve better. openclaw-mem competes on a different axis: governance. It captures agent activity as durable local records (SQLite + JSONL, no external database), then assembles bounded ContextPack bundles where every included memory carries a citation, every excluded memory carries a written reason, and every memory mutation ships with a rollback receipt.
Built sidecar-first for OpenClaw, usable with Claude, Codex, Gemini, and generic agent harnesses.
Not bigger memory — safer, explainable context.
Why agent memory needs governance, not just recall
Long-running agents don't just forget. Their memory degrades silently:
- Stale notes still match queries long after they stop being true.
- Untrusted or hostile content — tool output, scraped web text, injected instructions — retrieves well and slips into the prompt. This is the memory poisoning path of prompt injection, and similarity search alone cannot stop it.
- Context bloat: prompts swell into unbounded memory dumps nobody can review.
- No accountability: when the agent goes wrong, nothing explains why a memory was included.
The repository's own description, then 17% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.