Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
M

mex-memory/mex

Independent directory — not the official site. Details below come from the project's public repository.

Team memory for engineers and their AI agents.

1,797 ★ measured · checked 2026-11-19

Before you install: command ownership unverified - shown for reference only · license MIT

First step (reference only, ownership unverified): npx mex-agent@0.8.5 setup

★ 1,797·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
Official descriptionTeam memory for engineers and their AI agents. Lives in your repo. Shared through Git.

After install: how to tell it works

  1. What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
  2. One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
  3. If that does not work — This project has no troubleshooting notes. Search its issues for "install".

The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.

Star count
1,797 ★ · mex-memory/mex · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 1 sources
Score
score 107 · 1,797 ★ · 1 sources · repo
Install
see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Agent skills. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository mex-memory/mex;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

Shared project memory for engineers and their coding agents.

Excerpted from the repository README (abridged)

Memory lives as Markdown in .mex/, travels with Git, and stays linked to the code. Local Hub for people. CLI + skills for agents.
bash
npx mex-agent@0.8.5 setup
English | 简体中文 | Español | Português (Brasil)
Works with · Team memory · A teammate-handoff example · Project Hub · Quick start · How it works · Command map
### Works with
| Tool | What setup installs in 0.8 |
| Claude Code | Project anchor + skills (/mex-inbox, /mex-relay, /mex-statechart) |
| Codex | Project anchor + skills ($mex-inbox, $mex-relay, $mex-statechart) |
| Cursor, Windsurf, GitHub Copilot, OpenCode | Instruction anchor / template only — no official mex skill commands yet |
> [!IMPORTANT]
> MEX 0.8.5 turns complicated agent explanations into checked state diagrams. Ask your agent to explain a flow, bug, or recovery path with a statechart; read it in chat or explore it in Hub. This release also adds parallel, resumable setup and faster graph builds. Existing users should sync their project skills after upgrading.
One engineer knows why a constraint exists. Another has the debugging history. A coding agent found an important edge case in a session nobody else will read. The next teammate has to piece it together again.
What one engineer and their agent learn should become context the next teammate can use. MEX gives that knowledge a durable home in the repository: readable Markdown, code-linked explanations, reviewed knowledge contributions, and structured handoffs. People explore and review it in a local Hub; agents retrieve and help maintain it through project instructions and the CLI.
## What your team remembers
| What the team needs to retain | Where it lives in MEX |
| How the system works, and why | Wiki architecture, decisions, conventions, and patterns, with Code Graph grounding |
| A decision or explanation worth sharing | An Inbox proposal that adds to or corrects existing Wiki knowledge |
| Product requirements already captured | Existing Specs, requirements, constraints, and acceptance criteria remain supported |
| Where another engineer should continue | Relays with progress, decisions, blockers, evidence, and next actions |
| Earlier workflow context | Existing Workstream records remain readable |
| Who is involved, and what MEX recorded | Members and Activity history |
Canonical memory travels with ordinary Git commit, push, and pull. Each teammate keeps their own local indexes, drafts, identity selection, and Hub. No hosted MEX service, Docker, proxy, MEX account, or MEX-owned model key is required.
Working solo? The next person using that memory can be you in a new session.
## From one engineer to the next
An example: Alex changes webhook retry handling, and Sam will continue the work. Both are active MEX Members in a repository their team has already set up.
1. Start with the team's context. Alex asks Codex to inspect the existing architecture, relevant decisions, and code evidence before making the change and running tests.
2. Keep the useful discoveries. With Alex's direction, Codex updates the relevant Wiki explanation and code references. For a conclusion the team should review, it prepares an Inbox knowledge proposal for explicit approval.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/mex-memory-mex/)
Source
github · https://github.com/mex-memory/mex
Browse by field
Agent skills
Traction
1,797 ★
added
today

More entries

All 471 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index