hipocampus
Drop-in memory harness for AI agents, 3-tier memory, compaction tree, hybrid search. One command to set up. Works with Claude Code and OpenClaw.
Runs with mockssource: GitHubJavaScriptMITcommit df88ca19d42a
JavaScript, MIT licensed. The project labels itself: agent memory, ai agent, ai memory, claude code, compaction tree, context management, knowledge management and llm.
hipocampus runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Hipocampus v0.5.3 installs and runs in this container: init creates the full memory directory tree, skills, hooks, config, and platform-specific protocol files; compact processes transcripts through the daily/weekly/monthly compaction chain with secret redaction; uninstall removes all installed artifacts cleanly while preserving data;
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 92 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.
- npm install -g @tobilu/qmd failed — requires Node.js >=22.0.0 (container has v18.19.1) and EACCES on /usr/local/lib/node_modules
- npm link fails EACCES — cannot symlink into /usr/local/lib/node_modules
- Install time
- 1 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- node cli/compact.test.mjs passed all 13 assertions; node cli/init.mjs init --no-vector --no-search initialized all directories, skills, hooks, and config; TRANSCRIPT_PATH=... node cli/compact.mjs processed a 3-entry JSONL transcript through the compaction chain (daily→weekly→monthly) with secret redaction verified; node cli/uninstall.mjs removed all hooks, skills, and protocol blocks cleanly; --platform codex correctly produced AGENTS.md and .codex/hooks.json; --tenant produced isolated tenant directory with ROOT.md and config.
- Model tokens used
- 85,416
- Exact commit tested
- df88ca19d42a
- 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
- Behaviour against real services
- this run was verified against stand-in services only
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 attempt that decided the verdict above. 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.
=== Running tests ===
+ All secret scanner tests passed
=== Running help ===
hipocampus — Drop-in memory harness for AI agents
Usage:
hipocampus init Initialize memory system in current directory
Here is my complete findings report:
**ARGUSIC_RESULT:**{"install_succeeded":true,"launch_succeeded":true,"install_minutes":1,"errors":[…
tokens used
85,416
Here is my complete findings report:
**ARGUSIC_RESULT:**{"install_succeeded":true,"launch_succeeded":true,"install_minutes":1,"errors":[…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
- Installed in 1 minute, faster than the median of the 27 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 28 agent-memory projects Argusic has installed and timed, hipocampus was the 8th fastest to reach a running state, and 24 of 28 reached one at all.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Topics (from GitHub)
agent-memoryai-agentai-memoryclaude-codecompaction-treecontext-managementknowledge-managementllmlong-term-memoryopenclawragvector-search
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hipocampus)Questions
- Does hipocampus run?
- hipocampus runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test hipocampus?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit df88ca19d42a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test hipocampus?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hipocampus take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does hipocampus need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hipocampus?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does hipocampus compare with the alternatives?
- Of the 28 agent-memory projects Argusic has installed and timed, hipocampus was the 8th fastest to reach a running state, and 24 of 28 reached one at all.
- Where is the evidence for hipocampus?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.