memorix_project_contextLABSCO SUMMARY
Change the agent; keep the project memory.
Because the store lives under the Git project rather than inside one tool's session, what yesterday's Claude Code session worked out is available to today's Cursor session — and the review gate keeps that store from filling up with everything anyone ever typed.
What it is
A local-first shared memory layer for AI coding agents. SQLite is the canonical store and Orama handles search; project identity comes from the real Git root, so the memory belongs to the repository rather than to whichever tool you happened to use.
What you get
memorix_project_context— the default brief an agent starts from: current project facts, start-here files, selected evidence, cautions about stale or suspect memories, and lens-specific verification hints, with the task lens inferred from the request- Retrieval that expands only when needed:
memorix_search,memorix_detailfor a named missing fact,memorix_context_packfor a task-specific packet, andmemorix_graph_contextfor an evidence-governed graph overview - Writing memory:
memorix_store,memorix_store_reasoningfor design rationale with alternatives and trade-offs,memorix_search_reasoning,memorix_timelineandmemorix_resolve - Sessions:
memorix_session_start— which is also how an HTTP-mode agent binds the active repository — plusmemorix_session_endandmemorix_session_context memorix_evidenceandmemorix_feedbackfor the evidence and feedback lifecycles,memorix_codegraph_statusfor index counts,memorix_mediaas the compact media companion available in every profile, andmemorix_promotefor turning durable knowledge into reusable skills- Advanced tools registered only in the wider profiles:
memorix_knowledgefor the review-gated knowledge workspace, andmemorix_compaction_checkpointfor explicit continuity inspection - Git Memory turning commits into searchable engineering facts, orchestration for multi-agent work with handoffs, file locks and review loops, a local dashboard, and
memcode, a bundled terminal agent reading the same memory
Requirements
Node.js 22.18.0 or newer, and Git — project identity is derived from the real Git root, so a directory outside a repository has no identity to attach memory to. Install with npm install -g memorix, then memorix setup --agent claude --global, substituting the agent you use; setup covers Claude Code, Codex, Copilot, Cursor, Gemini CLI, OpenCode, Windsurf, Kiro and others, choosing plugin, MCP, rules, hooks or skills depending on what each supports. memorix init is optional and writes TOML configuration to ~/.memorix/config.toml globally or memorix.toml per project. Model keys are optional: without them, memory formation and embeddings are skipped and local full-text retrieval still works. Long-term memory is deliberately not automatic — a record has to be created and then approved, and only a manually created user item marked portable can be considered in another local project.
Setup effort
One command — npm install -g memorix
USE CASES
Stopping the re-explanation at the start of every session
The project-context brief hands a new session the current facts, the files to start from and the cautions, instead of you retyping the background.
Keeping knowledge when you switch tools
Memory is scoped to the Git project, so moving from one agent to another does not reset what the project knows.
Recording why a decision was made
Reasoning memory stores the rationale, the alternatives considered and the trade-offs, which is the part that normally disappears into an old chat.
Turning commit history into something an agent can use
Git Memory derives engineering facts from commits — what changed, where, and why it matters — rather than leaving the agent to read the log.
Keeping the memory store trustworthy
Durable records are candidates until reviewed; approval is an explicit operator step, and the lifecycle is recorded rather than silently overwritten.
Coordinating several agents on one repository
Orchestration covers task context, handoffs, file locks, verification gates and review loops, so parallel work does not turn into overlapping edits.
38 tools
Listed in project docs. Your client may show a different list.
memorix_codegraph_statusmemorix_context_packmemorix_graph_contextmemorix_storememorix_searchmemorix_detailmemorix_timelinememorix_resolvememorix_store_reasoningmemorix_search_reasoningmemorix_session_startmemorix_session_endmemorix_session_contextmemorix_evidencememorix_feedbackmemorix_retentionmemorix_consolidatememorix_deduplicatememorix_transfermemorix_suggest_topic_keymemorix_formation_metricsmemorix_audit_projectmemorix_skillsmemorix_promotememorix_workspace_syncmemorix_rules_syncmemorix_knowledgememorix_compaction_checkpointmemorix_mediamemorix_ingest_imagememorix_dashboardmemorix_pollmemorix_handoffteam_manageteam_messageteam_taskteam_file_lockBEFORE YOU INSTALL
What to know first
Tools you get
38 tools named in the project's documentation.
Requires
- memorix on PATH
- Node.js >=22.18.0
INSTALLATION
Connect your client
Server setup
npm install -g memorixMCP Clients
Claude Code
memorix setup --agent claude --globalCodex
memorix setup --agent codex --globalGitHub Copilot
memorix setup --agent copilot --globalCursor
memorix setup --agent cursor --globalPi Coding Agent
memorix setup --agent pi --globalGemini CLI
memorix setup --agent gemini-cli --globalOpenCode
memorix setup --agent opencode --globalWindsurf
memorix setup --agent windsurf --globalKiro
memorix setup --agent kiro --globalAntigravity
memorix setup --agent antigravity --globalTrae
memorix setup --agent trae --globalOpenClaw
memorix setup --agent openclaw --globalHermes Agent
memorix setup --agent hermes --globalCodeBuddy Code
memorix setup --agent codebuddy --globalOh My Pi
memorix setup --agent omp --globalDeepSeek Harness
memorix setup --agent dsh --globalAny MCP client — manual stdio
{
"mcpServers": {
"memorix": {
"command": "memorix",
"args": [
"serve"
]
}
}
}