M
mex-memory/mex
Team memory for engineers and their AI agents.
★ 1,797·更新 2026-11-19
在 GitHub 查看 ↗直链 · 无中转页
官方说明Team memory for engineers and their AI agents. Lives in your repo. Shared through Git.
装完之后怎么算装好了
- 装完该看到什么 — 命令正常结束时退出码为 0,终端里没有 "command not found" 或 "permission denied"。
- 一行自检 — 按该仓库 README 里给出的最小用法跑一次;能按 README 的描述输出就是通了。
- 答不出来怎么办 — 这个项目没有写排错说明,去仓库的 Issues 搜 install。
安装命令取自该仓库;以上判据只描述可观察到的结果,不替代项目自己的文档。
- ★ 数取值
- 1,797 ★ · mex-memory/mex · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 1 个来源列出
- 评分构成
- 综合分 107 · 1,797 ★ · 1 个来源 · repo
- 安装
- 安装命令见上方「安装与配置」。
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: Agent 技能。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
mex-memory/mex;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
Shared project memory for engineers and their coding agents.
以下摘录自该仓库的 README(片段)
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.
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.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/mex-memory-mex/)
- 来源
- github · https://github.com/mex-memory/mex
- 按领域浏览
- Agent 技能
- Traction
- 1,797 ★
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。