MEX CLI
Team project memory for engineers and agents: architecture, decisions and handoffs live in the repo and travel through Git
- 1,781 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs a local web server and indexes project code
- Changes agent instructions and adds files to the repo
Install
- Works in
Manual install
npx mex-agent@0.8.2 setupOpens setup in the local browser Hub. Add --cli for terminal setup.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs a local web server and indexes project code
- Changes agent instructions and adds files to the repo
This is third-party code. Review the repository files before installing.
What it does
MEX keeps a project wiki next to the code: architecture, decisions, conventions and patterns linked to code. Proposed knowledge changes land in an inbox and are accepted explicitly, and the mex-relay skill drafts a handoff for a teammate with progress, decisions, blockers and next steps. People browse and review memory in a local web Hub; agents read and update it through project instructions and the CLI. Everything is Markdown shared by ordinary commits, with no hosted service or account.
Who it is for. For teams where several engineers with agents pick up each other's work.
Good fit when
- Knowledge from agent sessions should persist and reach teammates
- You need to hand off unfinished work to another engineer with context
- You want architecture decisions in the repo with reviewed changes
Not a fit when
- The project is not in Git
- A simple note for one agent is enough; use CLAUDE.md or AGENTS.md
Example request
Draft a handoff of this task for Sam: what changed, which tests ran and what remainsLimitations
Requires Node.js 22.5 or later with SQLite FTS5 support and a Git repository. Memory population during setup is done by Claude Code or Codex CLI, which have their own account and network requirements. MEX never pushes or pulls; sharing happens only through your commits.
How to disable. Remove MEX files and pointers to them from agent instructions, then commit.
FAQ
Do I need a server or account?
No, memory lives in the repo and each teammate has their own local indexes and Hub.
Does a relay notify the teammate?
No, publishing only writes files. The teammate sees it after you push and they pull.
Discussion
No questions or reviews yet.
Related
CLI toolsPersistent agent memory in a folder of linked markdown notes, so Claude Code remembers a project across sessions
A long-term memory plugin that keeps decisions, preferences and task state across sessions and injects only what a query needs
Long-term memory for AI agents: Markdown files as the source of truth, a SQLite index as a cache, shared by Claude Code, Codex and others
Long-term agent memory in local Markdown files with a link graph, semantic search and MCP access
Long-term memory for agents: it distills knowledge from session history and brings it back in new tasks, one store shared across Claude Code, Codex, Cursor and
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
README in short
The README explains what knowledge a team keeps in MEX and walks through a handoff between two engineers. It describes the local Hub with wiki, code, inbox, relays and activity. Setup runs via npx mex-agent setup in the browser or with --cli in a terminal, with an optional contact form via Web3Forms at the end. MIT licensed.