explaingit

410979729/scope-recall

33Python

TLDR

scope-recall is a memory plugin for Hermes, an AI agent framework from Nous Research.

Mindmap

A visual breakdown will appear here once this repo is fully enriched.

In plain English

scope-recall is a memory plugin for Hermes, an AI agent framework from Nous Research. The job of a memory plugin is to decide what an AI assistant should remember between conversations and what it should not. This one is built around a specific complaint the README highlights: most agent memory tools either forget too much, so opening a new chat window means losing everything, or share too much, so a temporary note left in one group conversation leaks into another. The design splits memory into two layers and applies different rules to each. The first layer is a SQLite database treated as the authoritative truth store: every record lives here as plain rows that can be audited and rebuilt. The second is a LanceDB vector store, used as a companion for semantic search. LanceDB is rebuildable from the SQLite content, so if it gets corrupted or out of sync, it can be regenerated. Retrieval is hybrid, combining SQLite full-text search candidates with LanceDB semantic candidates, then rendering a bounded prompt. The scope rules are the heart of the project. Facts tagged as user preferences, explicit memories, project notes, or ops notes are shared durably across chat windows for the same user-plus-agent identity, so a decision made in one conversation can be recalled in the next. Raw general turn captures, the model's scratch notes from a single conversation, stay local to that chat, thread, or session and do not bleed into other contexts. Recall is current-turn scoped, meaning the plugin searches only for memories relevant to the active query, not for whatever was in the previous turn's buffer. Cross-scope governance actions like export, dedupe, or repair fail closed unless an explicit maintenance mode is set. Embeddings can run through a hosted OpenAI-compatible Gemini endpoint when an API key is configured, with a deterministic local-hash fallback so the plugin still works offline without keys. Installation is the standard Hermes plugin flow: clone into the plugins directory under HERMES_HOME, pip install in editable mode, set memory.provider to scope-recall in the Hermes config, and verify with hermes memory status. Python 3.11 or newer is required. An optional companion plugin called turn-closure-audit handles after-the-fact review of completed turns. The license is MIT.

Open on GitHub → Explain another repo

Generated 2026-05-21 · Model: sonnet-4-6 · Verify against the repo before relying on details.