mori vs mex
mori: Mori is a shared memory layer for AI coding agents that allows multiple instances to learn from each other, ensuring coherence and preventing 'cold starts'. It distills session activity into durable knowledge, enabling agents to start informed and benefit from collective intelligence.; mex: mex provides persistent, navigable project memory for AI coding agents, allowing every session to start with the right context instead of a cold prompt. It structures agent memory through a markdown scaffold, offers CLI tools for drift detection against the real codebase, and synchronizes context to keep agents aligned and reduce token usage.
TL;DR
Enabling AI coding agents across different machines or teams to share learned knowledge and maintain consistency.
- Your AGENTS.md or CLAUDE.md has grown too big and you want a small anchor plus routed context files.
- You want memory as plain markdown in the repo, reviewable in pull requests and diffable.
- You want drift checks that run without AI tokens and flag missing paths, stale files and broken scripts.
- You want recall across unrelated projects or conversations; mex lives inside one repository.
- You have a small project: another set of files to maintain may cost more than it saves.
- You expect the AST code-graph feature today: the README marks it as an unreleased preview.
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.