Memory your AI keeps
Local-first, persistent, per-project memory for your AI coding agents. Fully local. Fully yours.
Claude Code · Cursor · any MCP editor
# 1 · give your agent memory
$
# 2 · it just remembers — across sessions
remember("Deploy to prod from main on Vercel")
recall("how do we ship?")
→ "Deploy to prod from main on Vercel"
Norn is an MCP server over stdio, so it plugs into any MCP-compatible editor or agent — no per-tool adapter. A few of them:
Everything it does, and nothing it doesn't
A memory layer that earns trust by being legible. Nine honest capabilities — no magic, no lock-in.
100% local
Runs entirely on your machine, embedding model included. No API key, no cloud, no telemetry.
Per-project, committable
Each project gets its own isolated memory — export it to a diffable file and commit it with your repo.
Total control
A dashboard to see, search, and forget every memory. Nothing hidden.
Semantic recall
Finds memories by meaning, not keywords.
Norn Live
A real-time feed of every remember, recall, and forget — who acted, when, and what it touched.
Staleness surfacing
Quietly flags memories you haven't touched in a while, so you can prune.
Possible-conflict detection
Flags memories that might disagree and lets you choose — never auto-changes anything.
Works with your tools
Claude Code, Cursor, and any MCP-compatible editor.
Open source
MIT licensed. No lock-in.
Simple parts, fully in the open
A local store
SQLite plus a local embedding model, running on your machine. Your memory never leaves it.
Per-project isolation
Memory is scoped to each project and committed alongside the repo — portable, reviewable, yours.
You stay in control
Inspect, edit by forgetting, export and import. Every memory is visible and reversible.
Norn Live — watch your agents use memory
Every remember, recall, and forget streams into a live feed as it happens — who acted, when, and what it touched. Conflicts that need your call wait in a needs you panel until you decide.
Local like everything else: events live in the same SQLite file as your memories. And it only logs Norn's own tools — a trace of memory use, never a recorder of your prompts, code, or terminal.
- rememberclaude-codeDeploy to prod from main on Vercel
- recallcursor“how do we ship?” → 1 memory
- rememberclaude-codeRotate the signing keys every 90 days
- needs younorntwo memories may disagree — yours to resolve
example feed — your real one starts empty and fills as agents work
Give your agent a memory it keeps
One command, fully local. Open the dashboard whenever you want to see exactly what it remembers.
claude mcp add norn -- npx -y @samad001z/norn-server