Product problem
Coding agents forget everything between sessions. They lose standing rules when a long chat is compacted, bring back facts that stopped being true, and guess at dates and counts. Spookling Memory gives Claude Code and Codex a durable memory: a word-for-word log, dated facts that close themselves when something changes, and a timeline written by code instead of the model.
What I built
- Install and CLI.
npx spookling initis a wizard that installs the memory server, registers hooks and MCP servers for Claude Code, Codex, and the Claude desktop app, and offers to install Claude Code when it is missing.statusandupdatedetect older installs and repair them. - Team memory. Login, session upload when a session stops, an incremental org feed, per-session and per-project sharing, and team tools the agent can call. Uploads survive offline periods, rate limits, and sequence conflicts.
- Safety. Secrets are masked before anything leaves the machine, sessions are private by default, and a shared session shows colleagues the cleaned conversation only.
- Releases. Release branches, changelogs, and end-to-end sandbox tests covering install, login, share, unshare, and uninstall, across six public npm releases.
How memory works
Session ends ─► log ─► tagger quotes exact words ─► code dates, checks
Next question ◄─ rules + profile + dated facts + timeline + snippets
No model computes a date, writes a fact, or turns an answer into a refusal; code does. That is what keeps stale answers at zero.
Results
The team benchmarked Spookling Memory against keyword search over the same log, with the same answering model and one strict judge on both arms:
| Test | Spookling Memory | Keyword search |
|---|---|---|
| Facts that change (3 years of chats) | 103 of 106 | 37 of 106 |
| Stale answers | 0 | 18 |
| LoCoMo trick questions refused | 60 of 61 | 40 of 61 |
| LongMemEval (public, 470 answerable) | 81.5% | 82.6% |
LongMemEval is a statistical tie, reached with 13,900 tokens per answer against 39,900 for search.
Current work
I am building the cloud engine: an SQS worker with leases and epoch-fenced commits, versioned S3 snapshots, a FastAPI retrieval service that merges team spaces, and usage metering. It is in development and not part of the released results above.


