One SQLite brain, five agents, and you hold the delete key
Scope Recall gives Hermes, Codex, Claude Code, WorkBuddy and dsh a shared local long-term memory — with SQLite as the single source of truth and tools to audit every fact.
What it does
Scope Recall is a local memory core for coding agents. Multiple hosts — Hermes, Codex, Claude Code, WorkBuddy, and DeepSeek Harness — can attach to one shared SQLite store, so something you tell Codex can be recalled by Claude Code, with each memory recording which agent it arrived through. Facts are built from accumulated evidence rather than snap judgments on single sentences, and only the owner’s explicit correction changes them. Everything runs locally; the vector side (LanceDB by default) is a rebuildable companion, not the authority.
The interesting bit
The boring part is the point: SQLite is the only fact authority, and the vector index is disposable. That means you can inspect, correct, mute, or delete what’s remembered with plain CLI tools — including a secrets audit that lists stored credential matches by provenance so you can purge them. Private-mode rules can refuse capture, recall, or both, per session, directory, or the whole store, and events are judged by when they occurred, not when a retry happens to land.
Key highlights
- Shared store across five agent hosts, with per-agent provenance on every memory
scope-recall memorybrowses, searches, corrects, and deletes — no model calls involved- Export writes a portable package with sources, facts, history, and readable Markdown
- Private modes with stricter-rule-wins overlap and time-of-occurrence enforcement
- Synthetic recall benchmark covers retrieval, scope isolation, packet size, and latency — reproducibly, without a model or network
Caveats
- The benchmark uses a word-hashing embedder, so it says nothing about semantic embedding quality or performance on real private conversations — the README is upfront about this
- Upgrades are fussy: schema 1112 stores can’t be opened by earlier releases, 2.0.x needs an offline migration, and shared stores want a manual
vector_thresholdchange - Claude Code, WorkBuddy, and dsh are read-only entries; changes must go through Codex or a Hermes chat on the same store
Verdict
Worth a look if you juggle multiple agents and want memory you can actually audit and revoke. If you only use one host and don’t care what it remembers, this is more governance than you need.
Frequently asked
- What is 410979729/scope-recall-hermes?
- Scope Recall gives Hermes, Codex, Claude Code, WorkBuddy and dsh a shared local long-term memory — with SQLite as the single source of truth and tools to audit every fact.
- Is scope-recall-hermes open source?
- Yes — 410979729/scope-recall-hermes is open source, released under the MIT license.
- What language is scope-recall-hermes written in?
- 410979729/scope-recall-hermes is primarily written in Python.
- How popular is scope-recall-hermes?
- 410979729/scope-recall-hermes has 501 stars on GitHub.
- Where can I find scope-recall-hermes?
- 410979729/scope-recall-hermes is on GitHub at https://github.com/410979729/scope-recall-hermes.