hippo-memory
One memory for every agent you'll ever use. Hippo writes what you teach a coding agent into a store in your repo, and your other agents read that same store.
Runssource: GitHubhomepageTypeScriptMITcommit 36bb86905d0d
TypeScript, MIT licensed. The project labels itself: agent memory, ai agents, ai memory, claude code, claude code plugin, codex, coding agent and cursor.
hippo-memory runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install, npm run build (tsc), and npm test (vitest run) all succeed with 4212 passing tests. The hippo CLI binary runs and reports version 1.52.8. The doctor check reports only that no store has been initialized (expected in a fresh checkout) and that Claude Code is absent, which are not errors.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 in container but project requires >=22.16.01 minute
- Install time
- 8 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 465 test files, 4212 passed, 4 skipped; node bin/hippo.js --version returned 1.52.8; node bin/hippo.js doctor confirmed Node.js 22.16.0 operational
- Model tokens used
- 64,177
- Exact commit tested
- 36bb86905d0d
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
--no-learn Skip seeding memories from git history
remember <text> Store a memory
--tag <tag> Add a tag (repeatable)
--error Tag as error (boosts retention)
--pin Pin memory (never decays)
--verified Set confidence: verified (default)
--observed Set confidence: observed
--inferred Set confidence: inferred
All tests passed — 465 test files, 4212 passed, 4 skipped, 22 skipped (pre-existing). Here's the fi…
tokens used
64,177
All tests passed — 465 test files, 4212 passed, 4 skipped, 22 skipped (pre-existing). Here's the fi…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 27 comparable projects Argusic has measured.
Of the 28 agent-memory projects Argusic has installed and timed, hippo-memory was the 18th fastest to reach a running state, and 24 of 28 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-memoryai-agentsai-memoryclaude-codeclaude-code-plugincodexcoding-agentcursorgemini-cli-extensionllmllm-memorylocal-firstlong-term-memorymcpmcp-servermemorymodel-context-protocolopenclawopencodepersistent-memory
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hippo-memory)Questions
- Does hippo-memory run?
- Yes. hippo-memory runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test hippo-memory?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 36bb86905d0d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hippo-memory?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hippo-memory take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does hippo-memory need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hippo-memory?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does hippo-memory compare with the alternatives?
- Of the 28 agent-memory projects Argusic has installed and timed, hippo-memory was the 18th fastest to reach a running state, and 24 of 28 reached one at all.
- Where is the evidence for hippo-memory?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.