410979729

Scope Recall Hermes — Development skill for Claude Code

Development community

Local long-term memory for Hermes, Codex, Claude Code, WorkBuddy and dsh agents: one SQLite store, source-backed recall, and tools to inspect, correct or delete what is remembered.

How to install Scope Recall Hermes

This entry records only its repository, not the path inside it, so there is no exact command to give. Open 410979729/scope-recall-hermes and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Scope Recall Hermes does

Local long-term memory for Hermes, Codex, Claude Code, WorkBuddy and dsh agents: one SQLite store, source-backed recall, and tools to inspect, correct or delete what is remembered.

Alternatives in Development

  • Mem0 Chrome Extension — OpenMemory Chrome Extension: Long-term memory for ChatGPT, Claude, Perplexity, Grok etc 671 ★
  • Life Sciences — Repo for the Claude Code Marketplace to use with the Claude for Life Sciences Launch 308 ★
  • MoltBrain — Long-term memory layer for OpenClaw & MoltBook agents that learns and recalls your project context automatical 248 ★

README

Scope Recall

Scope Recall v3 is a bounded local memory core with SQLite as the authority and rebuildable vector companions. It provides host adapters for Hermes, and for Codex, Claude Code, WorkBuddy and DeepSeek Harness (dsh), which share one adapter of hooks and an MCP server (the MCP tools need the optional `codex` extra; dsh runs the hooks through a plugin). The public package is `hermes-scope-recall`; the Python import is `scope_recall`; the host wrapper identity remains `scope-recall`.

This checkout is `3.12.0`. Hermes, Codex, Claude Code, WorkBuddy and dsh can keep one memory: each attaches to a shared store as an entry, what the owner tells one of them another can recall, and each memory says which agent it came in through ([docs/shared-store.md](docs/shared-store.md)). An agent that is not attached keeps its own store. A tool's output is kept and found, but not turned into facts. Each release's notes are a line or two in [CHANGELOG.md](CHANGELOG.md) and in full on its [GitHub release](https://github.com/410979729/scope-recall-hermes/releases). Upgrading from `3.2.x` or later is `pip install -U`, `apply-install` and a host restart; the first store open adds the local management audit table. Back up before upgrading and follow the [management migration and rollback guide](docs/manage.md#migration-and-rollback). On a shared store in the shipped embedding space, set `vector_threshold` from 0.653 to 0.70 by hand ([docs/configuration.md](docs/configuration.md#vector_threshold)). Older supported stores migrate in order to schema 1111; an earlier release cannot open the upgraded store. Section 9 of the [3.1.0 release notes](https://github.com/410979729/scope-recall-hermes/releases/tag/v3.1.0) is the migration procedure for a 2.0.1 memory database. Facts are drawn from accumulated evidence rather than judged one sentence on sight; only the owner's explicit correction or confirmation changes a fact as it is captured. SQLite is the only fact authority; host adapte