susomejias/rembric

<p align="center"> <img src="./docs/banner.png" alt="Rembric" width="100%"> </p> <p align="center"> <b>Self-hosted memory, sessions, and dashboard for AI coding agents</b> </p> <p align="center"> <i>One Docker image, one process, one SQLite file. Multi-client by construction, reversible by design.</i> </p> <p align="center"> <a href="#supported-agents">Supported agents</a> · <a href="#quickstart">Quickstart</a> · <a href="#configuration">Configuration</a> · <a href="#dashboard">Dashboard</a> · <a href="#architecture">Architecture</a> · <a href="#project-status">Project status</a> · <a href="#contributing">Contributing</a> <br/> _{More docs: <a href="./docs/agents.md">Agent integration</a> · <a href="./docs/updates.md">Updates</a> · <a href="./docs/troubleshooting.md">Troubleshooting</a> · <a href="./docs/docker.md">Docker</a> · <a href="./docs/backup.md">Backup</a> · <a href="./docs/embeddings.md">Embeddings</a> · <a href="./docs/relations.md">Relations</a>} </p>

---

rembric /ˈrem.brɪk/ — coined, from remember + fabric: the woven memory and lifecycle layer beneath your agents. One brain, one dashboard, one audit trail — shared across every MCP-capable tool: Claude Code, Codex CLI, Hermes Agent, opencode, Cursor, and beyond. The MCP memory surface is the core; sessions, judgments, consolidation, and the operator dashboard come along in the same single Node process.

Supported agents

Rembric works with any agent that speaks MCP or HTTP. First-class plugins handle session lifecycle + per-project path-scoping automatically; everything else gets the same memory tools via a plain MCP URL.

<table> <tr> <td align="center" valign="top" width="25%"> <a href="./apps/plugin/README.md"><img src="https://matthiasroder.com/content/images/2026/01/Claude.png?size=120" alt="Claude Code" width="64" height="64" /><br/><b>Claude Code</b></a><br/> _{native plugin · 4 hooks · MCP} </td> <td align="center"