Hey everyone,
I’ve been building paradigm-memory, a local-first memory layer for AI coding agents.
The motivation is pretty simple: I got tired of agents forgetting project context, or relying on giant MEMORY.md files that slowly become a messy context dump.
paradigm-memory gives agents a persistent, searchable cognitive map instead.
GitHub:
https://github.com/infinition/paradigm-memory
Website:
https://infinition.github.io/paradigm-memory/
It is:
- local-first: one SQLite file on your machine
- MCP-native: works with Claude Code, Codex, Cursor, Cline, Continue, Gemini CLI, OpenCode, etc.
- auditable: every write / delete / import / move has a mutation log
- multi-agent: several agents can share the same memory store
- multi-workspace: one MCP process can serve multiple projects
- desktop inspectable: Tauri app with map, graph, search, review queue, audit log, snapshots and consolidation tools
- zero cloud / zero telemetry
The core idea is that memory should not just be a flat vector store.
Instead, facts live inside a cognitive map: nodes, items, keywords, importance, freshness, confidence, activation. When an agent calls memory_search, it gets a token-budgeted context pack with the relevant subtree and evidence, not 50 random chunks from a vector database.
Typical workflow:
- At the start of a task, the agent calls
memory_search. - It gets relevant durable project context.
- When it learns a decision, convention, bug, preference, or architecture detail, it writes/proposes it back to memory.
- You can review, edit, move, audit, export, import or consolidate everything from the desktop app.
Install is one line:
Windows:
irm https://raw.githubusercontent.com/infinition/paradigm-memory/main/scripts/installer/install.ps1 | iex
Linux / macOS:
curl -fsSL https://raw.githubusercontent.com/infinition/paradigm-memory/main/scripts/installer/install.sh | bash
Then:
paradigm
this is still early, but already useful in my own workflow. I’d especially love feedback from people using MCP-based coding agents: install flow, client compatibility, memory structure, and whether this kind of auditable local memory solves a real pain for you.