Scope Recall

What Scope Recall does

Scope Recall v3 is a bounded local memory core in which SQLite is the only authority for facts and vector indexes are rebuildable companions. Memory gathers evidence before a fact is written, rather than judging a single sentence on sight, and tool output is kept and findable but not turned into facts. The checkout described in the README is version 3.9.3. The public package is hermes-scope-recall, the Python import is scope_recall and the command is scope-recall.

Hermes, Codex, Claude Code, WorkBuddy and DeepSeek Harness can share one store, so what the owner tells one agent another can recall, and each memory records which agent it came through. An agent that is not attached keeps its own store. Two installed skills support this: scope-recall-setup for installation and upgrades, and scope-recall-memory for everyday questions such as what is remembered, whether the owner said it or it was inferred, and what correcting, muting or deleting a memory does.

Key features

• SQLite as the single fact authority with rebuildable vector companions
• Shared memory store across Hermes, Codex, Claude Code, WorkBuddy and DeepSeek Harness
• Each memory records the agent it came through
• Tools to inspect, correct, mute or delete remembered information
• Installed skills scope-recall-setup and scope-recall-memory

When to use it

• Keeping one shared memory between Hermes and a coding agent such as Codex
• Reviewing and deleting what an agent has remembered about you
• Asking the agent whether a remembered fact was stated by you or worked out

Who it is for: Hermes Agent users who want a local, auditable long-term memory that can also be shared with other coding agents.

How it fits with Hermes Agent

Built around Hermes Agent as its primary host with a Hermes adapter, and extended with adapters for other agents that share the same store.

Note: The README states that recall quality is not verified by an automated regression suite and that its accuracy figures were measured by hand on the authors' own corpora.

FAQ