OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Memory & RAG

Scope Recall

Scope Recall is a local long-term memory system for supported AI agents, using SQLite as its authoritative store and rebuildable vector companions for retrieval. Its host adapters let multiple attached agents share remembered information, while a local CLI supports inspection and management.

Official resource ↗Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Scope Recall — OpenViST project profile in Agent Memory & RAG.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Scope Recall when supported agent hosts need shared persistent context in a local store, or when an owner needs CLI tools to examine and manage what that store remembers.

Who it is for

  • People using supported agent hosts who want them to recall information from a shared local store.
  • Developers configuring persistent memory for Hermes, Codex, Claude Code, WorkBuddy or DeepSeek Harness.
  • Store owners who need to inspect, correct, mute or delete stored memories locally.

Documented uses

  • Share owner-provided context across attached agent hosts.
  • Retrieve remembered information with source provenance.
  • Browse memories and history, correct or mute facts, and delete conversations after reviewing dependent records.
Before you choose

Requirements & limits

  • Only hosts attached to the shared store can use its shared memory; unattached agents retain their own store.
  • LanceDB is the default vector backend and requires the lancedb extra; the sqlite-bruteforce option needs no extra and retrieves by words alone.
  • MCP tools for Codex, Claude Code, WorkBuddy and dsh require the optional codex extra.
  • Claude Code, WorkBuddy and dsh read memory through their tools; the README describes changes to shared memory as made in Codex or a Hermes chat on the same store.
  • The repository says tool output can be stored and found but is not turned into facts.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install the package with the documented vector and MCP extras

Prepare Scope Recall for a host using the default LanceDB vector store, with MCP tools available where the shared adapter is used.

Before you start

  • The same isolated Python environment used by the agent host.
  • A host supported by the corresponding Scope Recall adapter.

Steps

  1. Install or upgrade hermes-scope-recall[lancedb] in the host's Python environment.

  2. For Codex, Claude Code, WorkBuddy or dsh, install hermes-scope-recall[lancedb,codex] to include the MCP server's optional extra.

  3. Follow the project installation guide for the selected host and its store connection.

Expected outcome

The package and the selected optional dependencies are installed in the host environment; host-specific attachment is covered by the project installation guide.

Guide limitations

  • This package installation alone does not document a completed host setup.
  • LanceDB is required to open a store configured to use that vector backend.
  • The codex extra is needed for MCP tools on the shared adapter.
Documentation 1 ↗Documentation 2 ↗
Source-based practical guide

Browse and manage stored memories locally

Use the local maintenance CLI to search memories and review a deletion before applying it.

Before you start

  • An installed Scope Recall maintenance CLI.
  • Access as the local store owner.

Steps

  1. Run scope-recall memory to browse or search the store and inspect history.

  2. Use the documented memory-management commands to review the information associated with a conversation.

  3. For deletion, inspect the displayed dependent sources and facts before applying the change with --yes.

Expected outcome

The owner can inspect memory records and their history, and can review deletion dependencies before applying a conversation deletion.

Guide limitations

  • The management CLI operates locally as the store owner and makes no model request.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official resource ↗Official repository ↗
Source record details
Source availability
Active
Sources checked
23 October 2026
Original website title
410979729/scope-recall-hermes · Official homepage title · retained in its source language
How we review sourcesSuggest a correction