◆v0.2.0 · MIT · Local-first

Cross-agent memory that keeps the WHY.

The only MCP that solves agent amnesia. Metadata like "what was edited" isn't retrievable when it matters — an agent needs to know why you edited, why it failed, and how you fixed it. By keeping that context, linksee-memory prevents repeating mistakes across sessions and the gradual decay that hits every complex codebase as agents pile on unnecessary fixes and drift from the original axis.

Get started Star on GitHub

No account. No cloud. One SQLite file on your machine.

up to 99%

Tokens saved on re-reads

Memory layers

Cloud dependencies

Your agent, with memory

linksee-memory · local

Last week's deploy crashed — I think we fixed it somehow?

Let me check my caveats…

⚠️ caveatNextAuth sessions invalidate when JWT_SECRET rotates — redeploy all affected projects in parallel.

Right, that was it. Thanks.

Three pillars

Built on three things nobody else combines.

⚡

read_smart

Token savings, measured.

AST- and heading-aware diff cache on file reads. 86% saved on a typical TS edit, 99% on unchanged re-reads.

🔗

cross-agent

One SQLite file. Every agent.

Claude Code, Cursor, and ChatGPT Desktop share one brain at ~/.linksee-memory/memory.db. No cloud, no account, no lock-in.

🧠

WHY-first

Six layers, not a flat log.

goal / context / emotion / implementation / caveat / learning. Forgetting is tuned per layer — caveats are protected.

The WHY structure

Six layers that make retrieval explainable.

Every memory is tagged with exactly one layer. Recall composites relevance × heat × momentum × importance and returns match_reasons so you — and the agent — know why a row came back.

🎯

goal

The outcome the user is working toward. Persists across sessions so the agent doesn't drift.

🧭

context

Why this, why now. Surrounding constraints and stakeholders that shape the right answer.

💗

emotion

Tone cues from the user. Frustration, excitement, exhaustion — signals that change how to reply.

🛠

implementation

How something was done — including what failed. The difference between a clean diff and a scar.

⚠️

caveat

The "never do this again" drawer. Protected from auto-forgetting, always surfaced on recall.

🌱

learning

Patterns distilled over time. consolidate() compresses cold memories into protected learning entries.

Get started in 5 minutes

Not a developer? Start here.

We'll walk through everything — installing Node.js, setting up Claude Desktop, and verifying it works. No terminal experience required for Claude Desktop.

Claude Desktop (recommended for non-developers)

Claude Desktop uses a settings file. We'll add linksee-memory to it with one paste.

1
Open Claude Desktop settings
Launch Claude Desktop → Settings → Developer → "Edit Config". A JSON file opens in your editor.
2
Paste the linksee-memory block
Inside "mcpServers": { ... }, add the linksee key shown below. If mcpServers already has entries, add a comma before the linksee line.
```
"linksee": {
  "command": "npx",
  "args": ["-y", "linksee-memory"]
}
```
3
Restart Claude Desktop
Fully quit and reopen (not just close the window). linksee-memory loads on the next launch.
4
Verify it works
Start a new chat and type: "Can you remember that I prefer TypeScript over JavaScript?" Claude should confirm it saved this to linksee-memory.

How it compares

The features most agent-memory tools quietly skip.

Feature	Mem0 / Letta / Zep	Claude auto-memory	linksee-memory
Cross-agent (Claude + GPT + Gemini)	△	✕	✓
WHY-layered structure	✕ flat	✕ flat	✓ 6 layers
AST-aware file diff cache	✕	✕	✓
Active forgetting (curve-based)	△	✕	✓
Local-first · no account required	✕	✓	✓
match_reasons on recall	✕	✕	✓

Pro tier — Summer 2026

Cross-device sync and team sharing, on Pro

$19/mo. First 100 seats lock launch pricing forever. Cancel anytime — your memories stay in your local SQLite.

🔄

Cross-device sync

Start a task on your MacBook, continue on the office Linux box — the agent has the full context.

👥

Team-shared caveat layer

When one teammate's agent hits a pitfall, every other teammate's agent knows — no more repeating war stories across PRs.

🌐

Web dashboard

Browse, edit, and search your memories in a web UI. Export / import. See memory growth over time.

📈

Priority support + early access

Direct access to the builder. Responsive email support. Early access to experimental features (semantic recall, multi-agent coordination).

Who it's for: solo devs with multiple machines, or small teams (3–10) sharing agent workflows.

One email, max. No newsletter spam. Unsubscribe is just not replying.

Give your agent a brain it can trust next week.

MIT-licensed. One binary. Stays on your machine.

Get started Read the docs on GitHub