Memorix — Cross-Agent Memory Control Plane

Main

• Start with stdio (memorix serve) for one IDE/agent, then move to the HTTP control plane only when you need a shared background service and dashboard.

• Keep memory clean: README describes a pipeline for formation/dedup/consolidation/retention so memory stays useful instead of noisy.

• Use the operator CLI to audit and sync workspaces across tools; treat it as your “memory ops” surface while MCP remains the IDE integration layer.

Source-backed notes

• README positions Memorix as a local-first memory control plane for coding agents with cross-client support tiers (Core/Extended/Community).
• README quick start installs via npm install -g memorix then initializes config with memorix init and offers stdio (memorix serve) and HTTP modes.
• README documents an official Docker path for the HTTP control plane using docker compose up --build -d and exposes dashboard + /mcp endpoints.

FAQ

• Is HTTP required?: No — README recommends starting with local CLI/TUI or stdio MCP, and using HTTP only for a shared background control plane.
• Where is data stored?: README says it’s local-first and mentions SQLite as the canonical store; keep it on trusted machines.
• How do I connect an IDE?: Use the generic stdio MCP config (command: memorix, args: [serve]) shown in README examples.