SuperLocalMemory Logo — Local AI Memory Layer
SuperLocalMemory
v3.3.6 — Zero-Friction Hooks

Every Other AI Forgets.
Yours Won't.

Infinite memory for Claude Code. Install once — every session remembers the last. Automatically.

Auto-recall at start. Auto-observe during work. Auto-save at end. Zero commands. Zero config. Zero friction.

The Problem Every Claude Code User Hits

You spend 20 minutes explaining your project architecture to Claude Code. Your folder structure, your naming conventions, the reason you picked one ORM over another.

Next session: blank slate. Claude Code does not remember any of it.

Other memory tools exist, but they require you to manually call commands every session — recall, observe, save. That is ironic — a memory system you have to remember to use.

SuperLocalMemory v3.3.6 solves this. Install once. Memory works automatically, across every session, forever.

One Command. That's It.

Hooks auto-install. MCP auto-configures. Memory auto-activates. You do nothing.

1

Install SuperLocalMemory

terminal
$ npm install -g superlocalmemory

This installs the engine, Python dependencies, Claude Code hooks, and creates the data directory. Open Claude Code — memory is active.

What Happens Automatically After Install

Claude Code hooks installed

SessionStart, PostToolUse, Stop — all wired into settings.json

MCP server configured

Claude Code discovers SLM tools automatically

Session context injected

Every new session loads your project context before your first message

File changes observed

Every Write and Edit is silently captured with rate-limiting

Session summaries saved

Closing a session saves a summary with git branch, commits, and modified files

Future upgrades auto-applied

npm update triggers silent hook upgrade — no manual intervention

Advanced: Manual MCP Configuration

+

If hooks don't auto-configure your IDE, add this to your MCP settings:

MCP configuration
{
  "mcpServers": {
    "superlocalmemory": {
      "command": "slm",
      "args": ["mcp"],
      "type": "stdio"
    }
  }
}

The Automatic Memory Lifecycle

Six hooks that make memory invisible. You never think about it — it just works.

Auto-Recall at Session Start

SessionStart hook loads your project context, recent decisions, and learned patterns before your first message. Zero commands needed.

Auto-Observe During Work

PostToolUse hook silently captures file changes with rate-limiting. Every Write and Edit is observed — your coding decisions are remembered.

Auto-Save at Session End

Stop hook generates a session summary with git context — branch, commits, modified files. Next session picks up exactly where you left off.

Auto-Learn Patterns

After 20+ sessions, SLM optimizes retrieval for YOUR patterns. After 200+, a full ML model trains on your usage. Zero token cost.

Zero Risk, Zero Friction

Every hook wrapped with error absorption. Crashes are invisible. Hooks never block tools. Opt out anytime with one command.

Auto-Install, Auto-Upgrade

Hooks install on npm install and upgrade silently on version change. Old users and new users get the same zero-friction experience.

A Day With SuperLocalMemory

9:00 AM

Open Claude Code

SessionStart hook fires. Your project context, recent decisions, and learned patterns are injected before your first message. You see: "I recall you're working on the auth migration..."

9:15 AM

Write code

PostToolUse hook silently observes every file edit. Architecture decisions, naming choices, and bug fixes are captured. No commands needed.

10:30 AM

Session ends

Stop hook saves a summary: git branch, 12 commits, 8 files modified. The auth migration context is locked in.

2:00 PM

New session

SessionStart fires again. Full context from the morning is there. Claude Code picks up exactly where you left off — no re-explanation needed.

Next week

Different project

Switch to a new repo. SLM recalls that project's context instead. Each project has its own memory profile.

Under the Hood

Knowledge Graphs

Builds relationships between concepts, files, and decisions. Claude Code understands how parts of your codebase connect.

10.6ms Median Recall

Local SQLite with 5-channel hybrid search. No network latency, no API rate limits. Instant memory retrieval.

MCP Native

Built on the Model Context Protocol. No custom integrations — Claude Code speaks MCP natively. 30+ tools available.

100% Local & Private

Your code context never leaves your machine. No cloud APIs, no telemetry, no third-party servers. Works air-gapped.

74.8% on LoCoMo

Best-in-class for any local-only system on the standard long-conversation memory benchmark. No cloud dependency.

17+ AI Tool Support

Same memory works with Cursor, Windsurf, VS Code, ChatGPT Desktop, and more. Set up once, remember everywhere.

What Claude Code Remembers

Architecture Decisions

Folder structure, module boundaries, dependency choices, and the reasoning behind each one.

Code Conventions

Naming patterns, formatting preferences, TypeScript strictness, import ordering, testing conventions.

Debugging History

Known issues, workarounds, edge cases investigated, bugs fixed and the root causes found.

Session Context

What you worked on in each session — git branches, commits, modified files, and progress.

Preferences & Patterns

How you like explanations, your communication style, tools you prefer, approaches you've approved.

Cross-Session Decisions

Trade-offs discussed over multiple sessions. Why you chose one library, rejected another, pivoted on a third.

30+ MCP Tools for Claude Code

Beyond auto-memory, SLM gives Claude Code a full memory toolkit.

session_init

Load full context at session start

remember

Store knowledge with importance scoring

recall

5-channel hybrid search across all memories

observe

Silently capture content worth remembering

search

Full-text search across memory graph

build_graph

Build knowledge graph from memories

get_learned_patterns

Retrieve patterns learned from your usage

consolidate_cognitive

Merge related memories automatically

get_soft_prompts

Context-aware prompts from your history

recall_trace

Trace how a memory was retrieved

fetch

Direct memory access by ID

get_behavioral_patterns

Patterns detected from your workflow

Frequently Asked Questions

How does auto-memory work in Claude Code?

+
SuperLocalMemory v3.3.6 installs Claude Code hooks automatically. SessionStart recalls your context, PostToolUse observes your work silently, and Stop saves a session summary. You never call any commands — it just works.

Does SuperLocalMemory send my code to the cloud?

+
No. SuperLocalMemory is 100% local. All data stays in SQLite on your machine. Zero network calls, zero telemetry, zero cloud dependency. EU AI Act compliant.

What if I don't want auto-hooks?

+
Run 'slm hooks remove' to opt out. A .hooks-disabled marker ensures auto-install never re-enables them. Run 'slm hooks install' anytime to opt back in.

Does it work across Claude Code sessions?

+
Yes — that's the core value. Every session starts with your full context auto-loaded. Architecture decisions, naming conventions, debugging history, preferences — all recalled instantly.

Can I use the same memory with Cursor and other AI tools?

+
Yes. SuperLocalMemory uses the MCP protocol. The same memory database works across Claude Code, Cursor, Windsurf, VS Code, ChatGPT Desktop, and 17+ other AI tools.

Will hooks slow down my Claude Code sessions?

+
No. All hooks are wrapped with error absorption (crashes are invisible). The fast path checks a single file (~0.1ms). Hooks never block tool calls — they observe silently.

Do hooks work with parallel agents and subagents?

+
Yes. v3.3.6 removed the PreToolUse gate that caused issues with parallel agents. Hooks are observation-only — they never block any tool calls, so agents run at full speed.

Works With Your Entire AI Toolkit

The same memory database works across all MCP-compatible tools. Install once, remember everywhere.

Every Other AI Forgets. Yours Won't.

Open source. AGPL v3. One command to install. Infinite memory for Claude Code.