I've been using AI agents like Claude Code and Cursor for a while, and the biggest headache was simple: every new session, the agent starts from zero. It forgets the bug we were debugging, the project conventions I set two days ago, and that weird API quirk we already solved. Each conversation is a fresh slate.
Sure, some agents have built-in memory, but it's often limited to the same session or requires patching the agent itself. I didn't want to modify the internals of tools I depend on. What I needed was a separate process that could watch my sessions, build a knowledge base, and feed relevant context back without touching the agent.
That's why I built Memory Sidecar. It's a production memory system that runs alongside your agent — Hermes, Claude Code, Cursor, Codex, any of them — and gives it real memory. It doesn't patch the agent. It's a sidecar: a completely separate process that shares a data directory.
How it works
The sidecar monitors the agent's session data (state.db and session files). Every time the agent writes a checkpoint, the sidecar picks it up and processes it through three retrieval layers:
