SuperLocalMemory icon

SuperLocalMemory

SuperLocalMemory is an open-source, local-first memory control plane for AI agents and teams, with governed recall, corrections, shared memory, and optional media search.

SuperLocalMemory

Local memory control for AI agents

SuperLocalMemory is an open-source, local-first memory control plane for AI agents and teams. It stores decisions, documents, and other project information on a user's machine, then makes that information available through recall instead of leaving each agent session with isolated context.

Its core design emphasizes governed retrieval: results can identify an exact supported answer, show the closest available memories when the match is incomplete, or state that the information is not present. In the documented local Mode A, core remember and recall do not require a model-provider call, API key, cloud account, or Docker.

The project can connect multiple agents through MCP or commands and includes optional indexing for pictures, screenshots, and PDFs. It also provides workflows for replacing outdated memories, reviewing corrections, and sharing memory through a governed mesh.

Key features

Local-first text memory

Mode A keeps core remember and recall on the user's machine without a model-provider call, cloud account, or Docker requirement.

Explicit uncertainty handling

Recall distinguishes supported answers, close-but-not-exact matches, and cases where the requested information is not present, rather than always returning an apparently relevant result.

Governed corrections

Memories can be categorized, replaced, reviewed, and rolled back. The documented CLI example updates a staging database fact with --replaces and exposes a correction review workflow.

Shared and governed memory

The project is designed to share memory between local agents and web bots through a mesh, with access governed as company data. The repository also includes documentation for team and shared-memory workflows.

Optional media retrieval

An optional media mode indexes pictures, screenshots, and PDFs with a second local model, allowing text and media to be returned from one recall operation.

Agent connections

It offers command-line access, MCP support, and documented connection or plugin paths for multiple coding agents and desktop tools.

Use cases

  • Persistent project context

    Record architecture decisions, deployment procedures, and environment facts once, then make them available to coding agents across sessions instead of re-explaining the project each time.

  • Team and multi-agent knowledge

    Connect several local agents and web-facing bots to a shared memory mesh so a team can use common decisions and documents while retaining governed access to the information.

  • Evidence-aware agent workflows

    Use the recall behavior when accuracy matters: accepted answers are separated from close matches, and absent information is returned as absent rather than silently filled with a guess.

  • Searchable visual and document archives

    Enable the optional media mode when project knowledge includes screenshots, scanned material, PDFs, or other pictures that users need to find by description.

  • Maintained operational knowledge

    Correct changing operational facts such as database versions, ports, or deployment procedures by replacing an older memory and retaining a review or rollback path.

Pros and Cons

Pros

  • Core text memory can run locally in Mode A without a model-provider call, cloud account, or Docker.
  • Retrieval behavior explicitly handles missing or uncertain information instead of treating every search result as a verified answer.
  • The project supports multiple agent connections and provides correction, replacement, review, and shared-memory workflows.
  • Optional local media retrieval extends recall to pictures, screenshots, and PDFs.

Cons

  • The product is primarily a developer-oriented, command-line and integration-driven tool; setup involves connecting it to the agents or tools being used.
  • Media indexing is optional rather than part of the base text workflow and has additional local resource requirements documented by the project, including about 1.5 GB and 16 GB of memory.

FAQ

How is SuperLocalMemory installed?

SuperLocalMemory can be installed through an agent-guided setup flow, the macOS/Linux shell installer, npm, pip, uv, or a repository install script. The README also documents setup and connection commands for supported tools.

Does it require a cloud account or model-provider API key?

In Mode A, core remember and recall do not make model-provider calls, and the memory stays on the local machine. Optional features that send data out are described separately in the documentation, so users can choose whether to enable them.

Can it search pictures and documents as well as text?

Text is searched with a local text model. If pictures and documents are enabled, a second local model handles those files, and a recall can return results from both text and media.

How do agents connect to the memory system?

The project provides commands such as slm connect for connecting agents, and supports agents or harnesses that speak MCP or run a command. The repository lists connection paths for tools including Claude Code, Codex, Cursor, Windsurf, Zed, Claude Desktop, JetBrains, and OpenCode.

Quick Facts

Category
Developer Tool
Primary users
AI agent users and teams
Deployment approach
Local-first; Mode A keeps core memory on the user's machine
Access methods
CLI, MCP, and agent integrations
Supported systems
Windows, Linux, and Apple Silicon macOS
Source
Open-source GitHub repository