LongMemory
Local persistent memory store for LLM applications including claude desktop, github copilot, codex, antigravity, etc.
Runssource: GitHubhomepageTypeScriptApache-2.0commit 9ee2c8e1ed42
TypeScript, Apache-2.0 licensed. The project labels itself: ai, ai agents, ai infrastructure, ai memory, artificial intelligence, cognitive architecture, embeddings and gemini.
LongMemory runs. An Argusic agent installed it in 5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
LongMemory CLI, HTTP server (port 7331), and programmatic library all function: init, status, ingest, recall, and health endpoints work with SQLite persistence.
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.
- System Node.js is v18.19.1 but project requires >=202 minutes
- better-sqlite3 install script errored on node_gyp_bins lstat after successfully building the .node binary
- keytar native build failed: missing libsecret-1-dev system library
- Install time
- 5 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm build exited 0; curl http://127.0.0.1:7331/health returned 200; curl POST /v1/ingest returned node data; curl POST /v1/recall returned 2 items; library API createMemory/ingest/recall cycle returned correct data; CLI --help listed 25 commands
- Model tokens used
- 208,436
- Exact commit tested
- 9ee2c8e1ed42
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here's my full test report: **Install:** Cloned the repo, installed Node.js v22.14.0 from binary (system had v18), used its bun… **Issues encountered:** 1. **System Node.js v18 too old** — Project requires `>=20`. Fixed by downloading Node.js v22.14.0 … 2. **better-sqlite3 native build caused a non-fatal node-gyp ENOENT error** after successfully buil… 3. **keytar native build failed** — Requires `libsecret-1-dev` (no root to install), but keytar is … **Verification:** - `node dist/cli/index.js --help` returned JSON with 25 commands - `node dist/cli/index.js init` + `node dist/cli/index.js status` showed 18 worlds ready - Server started on port 7331, health endpoint returned `200` - Ingestion and recall via HTTP API returned results (2 items found after ingesting twice) - Programmatic library API: `createMemory()` → `ingest()` → `recall()` returned the stored memory
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 3 errors 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.
What did not, or is not known
- Took 5 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, LongMemory was the 123rd fastest to reach a running state, and 166 of 235 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 5 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)
aiai-agentsai-infrastructureai-memoryartificial-intelligencecognitive-architectureembeddingsgeminillmlong-term-memorylongmemorymemorymemory-enginememory-retrievalollamaone-lineopenairagsupermemoryvector-database
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/longmemory)Questions
- Does LongMemory run?
- Yes. LongMemory runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test LongMemory?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9ee2c8e1ed42. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test LongMemory?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does LongMemory take to install?
- 5 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 LongMemory need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing LongMemory?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does LongMemory compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, LongMemory was the 123rd fastest to reach a running state, and 166 of 235 reached one at all.
- Where is the evidence for LongMemory?
- 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.