Skip to content

Questions about hippo

How do I give Claude Code memory between sessions?

Run npm install -g hippo-memory, then hippo init in the project. Init adds a short block to an existing CLAUDE.md and installs hooks that keep pinned memories in context, save your task before compaction, store failed tool calls and run hippo sleep when the session ends.

How do I give Cursor memory between sessions?

hippo init adds its instructions to AGENTS.md if the project has one, which Cursor reads. Add hippo mcp to .cursor/mcp.json and Cursor's agent gets tools to recall and store memories. hippo import --cursor .cursor/rules turns your existing rules into memories.

Which agents does hippo work with?

hippo init detects Claude Code, Codex, Cursor, OpenClaw, OpenCode and Pi, and wires itself into each one's instruction file, hooks or plugin. What runs automatically differs by agent. Any MCP client can use the MCP server, and anything else can call the CLI.

Can I use hippo as an MCP memory server?

Yes. hippo mcp runs the server over stdio. Add it to the MCP config of Cursor, Claude Desktop, Windsurf (now Devin Desktop), Cline or any other client, or in Claude Code run claude mcp add hippo-memory -- hippo mcp.

How is hippo different from mem0?

mem0 uses a language model to extract memories, and its hosted MCP server keeps them in your Mem0 account (mem0 docs (opens in new tab), checked 2026-09-28). Hippo stores memories in SQLite on your machine and needs no account and no model. On LoCoMo, a public test of questions about long conversations, Mem0 scored 94.9 and hippo 89.4 when we ran both.

Is this just RAG?

Partly. Recall is search, BM25 plus embeddings if you install them. The difference is that the store changes as your agent works. A memory you mark wrong drops down the results, a newer fact replaces an old one, and unused memories fade.

Does it need embeddings?

No. Recall runs on BM25 out of the box, with no model and no network call. With the optional free local embedder on, hippo scored higher than without it on two of five public answer tests, by 3.4 and 11.9 points, with no clear difference on the other three.

Do I still need CLAUDE.md?

Yes, for short standing rules such as build commands and code style. Claude Code's memory docs (opens in new tab) say that when two rules contradict each other, Claude may pick one arbitrarily. Hippo holds the lessons that pile up and recalls the ones that match the task.

What happens when a memory turns out to be wrong?

hippo outcome --bad weakens the memories from the last recall, and hippo supersede <id> "<new fact>" replaces one. On a synthetic test where every mark was correct, a bad mark cut how often a wrong memory stayed in the top five from 71.9% to 0.0%. Real marks are noisier.

Where does hippo keep my data?

On your machine, in SQLite, as .hippo/hippo.db in each project and a global store in ~/.hippo/, with markdown mirrors you can read and commit. Recall makes no network call by default. Text leaves your machine only through an API embedder, a reranker, model-read rule capture (capture.followUpRules), hippo refine, or hippo sleep when ANTHROPIC_API_KEY is set. {"extraction":{"enabled":false}} in .hippo/config.json turns that last one off.

What does hippo cost?

Nothing. Hippo is MIT-licensed and needs no account or API key. Optional features that call an outside provider bill through it. The Jev reranker costs about 0.0004 USD a recall, and API embedders and sleep's fact extraction use your own keys.

Is it production-ready?

Judge it by what is tested. 3,500+ tests run against a real database, with no module mocks and no mocked store. It has zero runtime dependencies. The next question covers what it does to an agent's work.