Agent memory
Agent memory is information that an AI coding agent keeps between sessions, so that it does not start every session blank.
How Aletheia does it
Aletheia (npm package aletheia-mem) installs hooks into each coding tool. The hooks capture prompts, tool calls and the end of a turn. They redact secrets and <private> blocks before anything is stored. The result goes into one SQLite file with full-text search (FTS5), and a short context block comes back when the next session starts.
Any tool can also read the same store over MCP, REST or the command line.
What is not checked
Hooks have run in real sessions of Claude Code, Command Code and Codex CLI: one user on one machine. Cursor, Gemini CLI and Windsurf are configuration written from their documentation, not tested on a real install. Answer accuracy is not measured; the benchmarks measure retrieval only.
Questions and answers
- Where does Aletheia store memory?
- In one SQLite file on your machine.
- Can other tools read the same memory?
- Yes, over MCP, REST or the command line.
- Is the accuracy of the answers measured?
- No. The benchmarks measure retrieval only.
Related projects
- Aletheia: A free, local memory and rules hub for AI coding tools.
Sources
- Aletheia README, read 2026-10-30
- Aletheia documentation: how it works, read 2026-10-30