MEX uses Git itself as a shared context layer for coding agents and teams
DJIRNMAN · reddit · 2026-09-09
The author open-sourced MEX (mex-memory/mex), a Git-native shared memory layer for coding agents and engineering teams.
Core idea: what team memory needs — history, diffs, changes moving with the repo, per-branch state, visible conflicts — Git already does, so skip the database/sync/accounts stack.
- Memory as files: architecture, decisions, specs, workstreams, handoffs, and activity get committed like code
- Local indexes stay local: each checkout rebuilds its own search and code-intelligence indexes
- Memory shares code history: decision changes are reviewable via diff, conflicting edits surface as Git conflicts, and agent learnings survive the session
- Structured handoffs: agents prepare handoffs with completed work, blockers, decisions, changed files, and next actions, committed into project history
- No silent truth: shared changes go through a proposal flow — publishing and accepting a Spec are separate, explicitly approved actions
Tradeoffs: Git isn't a realtime bus, MEX doesn't auto push/pull, and disconnected clones still produce normal conflicts. The author argues project memory should behave more like source code than another SaaS database.
Related event: MEX: Using Git as Shared Memory Layer for Coding Agents(2 posts)→
More from coding & agent
- Eraser Open-Sources AI-Native, Coordinate-Aware Diagram Format — yawnxyz · 2026-09-09
- Code formatting was solved in the 80s: Ada's DIANA IR stored no text sources at all — maxleiter · 2026-09-09
- QA Engineer Uses Codex to Learn DevOps, Then Wonders What's Left to Learn — Recent-Tangerine2745 · 2026-09-09
- WebMCP Gains Steam: MCP Tools Embedded in Web Pages for Browser Agents, No Server Needed — every · 2026-09-09
- Reducto doubles Extract speed, hits 99% citation coverage, flat 2¢/page pricing — ycombinator · 2026-09-09
- Vercel Switches to Flat-Rate CDN Pricing to End Surprise Bandwidth Bills — cramforce · 2026-09-09