Cross-agent memory that outlives your IDE tab
Memorix is a local-first MCP server that gives coding agents persistent, shared project memory across sessions and editors.

What it does Memorix acts as a local control plane for coding agents, storing project context, reasoning chains, and Git-derived facts in a SQLite database so work can survive across IDE switches and terminal sessions. It exposes a Model Context Protocol (MCP) server that plugs into Cursor, Claude Code, Codex, Windsurf, and a dozen other clients, plus a TUI workbench and CLI for direct operator control. The goal is to stop every agent thread from starting with a blank slate.
The interesting bit Instead of treating memory as a simple key-value dump, Memorix runs a quality pipeline—formation, deduplication, consolidation, and exponential-decay retention—to keep the store useful rather than noisy. It also attempts to sync workspace rules and MCP configs across editors, which is the kind of glue work that usually gets left to shell scripts and hope.
Key highlights
- Three-layer memory: observations, reasoning context, and immutable Git-derived facts with noise filtering.
- Cross-agent sync via MCP, with tiered support: “Core” for Cursor/Claude Code/Windsurf, “Extended” for Copilot/Kiro/Codex, and “Community” for the rest.
- Optional autonomous-agent team features: task boards, inter-agent messaging, advisory file locks, and a structured orchestration loop for multi-agent work.
- Local-first stack: SQLite as the canonical store, Orama for search, no cloud dependency.
- Built-in TUI dashboard and web UI for browsing memories, sessions, and agent team state.
Caveats
- Docker support is limited to the HTTP control plane, and project-scoped Git behavior requires the container to see the bound repositories.
- Client support is tiered: “Extended” and “Community” integrations come with platform caveats or best-effort compatibility.
- The stdio MCP path and HTTP background mode are separate concerns, so picking the wrong launch mode for your setup means missing features.
Verdict Worth a look if you juggle multiple AI coding agents and want project context to persist across them. Skip it if you live in a single IDE with a single agent and are happy with its built-in memory.
Frequently asked
- What is AVIDS2/memorix?
- Memorix is a local-first MCP server that gives coding agents persistent, shared project memory across sessions and editors.
- Is memorix open source?
- Yes — AVIDS2/memorix is open source, released under the Apache-2.0 license.
- What language is memorix written in?
- AVIDS2/memorix is primarily written in TypeScript.
- How popular is memorix?
- AVIDS2/memorix has 566 stars on GitHub.
- Where can I find memorix?
- AVIDS2/memorix is on GitHub at https://github.com/AVIDS2/memorix.