mex vs operator-memory
A living wiki for your codebase, written by your coding agents: a Tree-sitter graph grounds structured Markdown notes, task-aware routing loads only what's needed, and drift checks catch stale claims. — versus — Context engine for coding agents: each session consults, then updates, a Markdown brain of specs, decisions, standards and lessons — private, team-shared via Git, and per-user. No embeddings.
Both have coding agents write and maintain living Markdown docs of the codebase. mex grounds notes in a Tree-sitter graph and checks drift; Operator relies on the agent's consult-build-update loop.
| mex | operator-memory | |
|---|---|---|
| Stars | 1.8k | 500 |
| Forks | 153 | 19 |
| Language | TypeScript | TypeScript |
| License | MIT | BSD-3-Clause |
| Last activity | 2 days ago | yesterday |
| Topics | code-intel, memory | memory, coding |
| Curated connections | 6 | 5 |
mex — the curator's take
The answer to the instruction file that grew to 2,000 lines: knowledge lives in a routed `.mex/` wiki instead of one giant prompt, claims can be grounded to exact graph nodes by fingerprint, and `mex check` validates paths, commands, links, indexes and symbols spending zero tokens before `mex sync` sends the agent to repair only what drifted. Code stays the source of truth; the wiki is its maintained explanation. Limits worth knowing: the deterministic graph covers TypeScript/TSX, JavaScript/JSX, Python and Rust, so a polyglot monorepo outside that set gets a thinner spine — and the wiki is only as good as what your agents write into it, so it needs review like any other docs.
operator-memory — the curator's take
Use it when you want agent memory that looks like project documentation: specs and decisions the agent keeps current, readable in a diff and shareable with your team by committing .operator-shared/. Works across Claude Code, Codex, OpenCode, Pi and DeepSeek's harness with no background service or vector DB. NOT a recall store for chat transcripts or fuzzy retrieval — a cold project starts with a sparse brain until you ask for the first specs, and it relies on the agent choosing to update docs, so long sessions can drift.