ownmem

Open-source, Git-native memory for AI coding agents, deterministic local recall for Claude Code, Codex, Cursor, Gemini CLI, and compatible tools.

Runssource: GitHubhomepageJavaScriptApache-2.0commit f75cd4bb1834

JavaScript, Apache-2.0 licensed. The project labels itself: agent memory, ai agent memory, ai memory, bm25, claude code, claude code memory, codex and codex memory.

ownmem runs. An Argusic agent installed it in 3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All ownmem tests (structure, public, and tokenizer) pass; benchmark achieves 100% Recall@1 with deterministic local retrieval; CLI help and init --preview both respond correctly.

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
428
forks
10
open issues
0
watchers
3
size
3 MB
created
last push

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.

Time lost to each failure while testing ownmem, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

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 is pre-installed but ownmem requires >=20.6.02 minutes
Install time
3 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm test exited 0: 'repository structure self-test: passed' and 'memory public self-test: passed on linux x64'. node test/tokenizer-multilingual-self-test.mjs exited 0: '12/12 passed'. npm run benchmark exited 0 with R@1 100.0%, MRR 1.0000, P95 1.08ms, quality & performance gates passed. ownmem --help printed usage. ownmem init --check printed drift preview.
Model tokens used
75,844
Exact commit tested
f75cd4bb1834
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 2, 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.

Release gate: not measured
Controls: model_calls=0, network_calls=0, corpus=c62472293bd15e4581725358ff6e13762b5f4b2d659db30c19…
All good. Here's the summary:
**Install:** `npm install` added 6 packages without errors. The only environment gap was Node.js (v…
**Tests:** All three test suites pass and the benchmark runs correctly.
**CLI:** `ownmem --help` and `ownmem init --check` both work as expected.
tokens used
75,844
All good. Here's the summary:
**Install:** `npm install` added 6 packages without errors. The only environment gap was Node.js (v…
**Tests:** All three test suites pass and the benchmark runs correctly.
**CLI:** `ownmem --help` and `ownmem init --check` both work as expected.

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.
  • Installed in 3 minutes.
  • 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 28 agent-memory projects Argusic has installed and timed, ownmem was the 11th 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 3 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.01
Argusic Runner1/3Did not run20.000.01

Topics (from GitHub)

agent-memoryai-agent-memoryai-memorybm25claude-codeclaude-code-memorycodexcodex-memorycoding-agent-memorycoding-agentscursorcursor-memorydeterministic-retrievaldeveloper-toolsgemini-cligemini-cli-memorygit-nativellm-memorylocal-firstproject-memory

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/ownmem.svg)](https://argusic.com/subject/ownmem)

Questions

Does ownmem run?
Yes. ownmem runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test ownmem?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f75cd4bb1834. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ownmem?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ownmem take to install?
3 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 ownmem need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ownmem?
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 ownmem compare with the alternatives?
Of the 28 agent-memory projects Argusic has installed and timed, ownmem was the 11th fastest to reach a running state, and 24 of 28 reached one at all.
Where is the evidence for ownmem?
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.

Discussion