MEX 0.8.5 turns coding agent explanations into checked state diagrams
MEX 0.8.5 adds a statechart skill that has Claude Code or Codex draw a flow as a state diagram, with project notes and code references attached. The useful part is what it does to recovery paths.
The maintainer of MEX, an open-source project memory tool for Claude Code and Codex, shipped a skill that turns long agent explanations into state diagrams built from a project's own notes, and r/AI_Agents had thoughts.
You know the feeling. You ask Claude how some flow works, it gives you six tidy paragraphs, you read every word and you still can't picture what happens when step four fails.
That's the problem behind a post on r/AI_Agents this week from the person who maintains MEX. Their fix was a state diagram skill. The thread is small, 14 points and 13 comments, but the idea is worth copying.
The pitch is simple. As the post puts it, "You can already ask Claude for Mermaid." What they wanted on top of that was a diagram that pulls in the decisions and gotchas the project has already written down, with sources you can open and check.
What's actually new
MEX itself isn't new. Its README calls it "shared project memory for engineers and their coding agents." It keeps a team's architecture notes, decisions, requirements and handoffs as Markdown inside the repo, uses Git as the sharing layer and builds local SQLite indexes on each machine. There's no hosted MEX service, no MEX account and no model key of its own.
Version 0.8.5 is the new bit. The README says it "turns complicated agent explanations into checked state diagrams." You ask your agent to explain a flow, a bug or a recovery path as a statechart, then read it in chat or open it in the local Hub, which listens on 127.0.0.1. In Claude Code the skill is /mex-statechart and in Codex it's $mex-statechart. Cursor, Windsurf, Copilot and OpenCode get instruction files but no official skill command in 0.8.
The example in the post is MEX's own setup and recovery flow, and tbh it's a good one. The first pass over the code covered the normal stuff: pauses, retries and saved files. Then a project note surfaced an awkward case. If you rebuild the CLI while an old setup process is still running, the rebuild can remove a module that process still references. Hitting Retry doesn't help, because it doesn't replace the cached imports the old process is holding.
Keep reading
Related articles
DeepSeek open-sources dsh-superagent, a Router-Worker coding agent
DeepSeek's Harness team published dsh-superagent, a research prototype that splits a coding agent into one Router and many isolated Workers on a single GitHub repo. Its permission model is the part worth stealing.
Context.dev raises $9M seed to give agents live web data
Context.dev raised a $9M seed led by General Catalyst for one API that searches, scrapes and monitors the web for agents. Builders on Reddit cared less about the money than about how scrapers fail.
Construct lets agents describe 3D objects instead of drawing them
An agent researches a real object and writes down what it knows, then Construct turns that into a 3D model with each part tagged by how it is known, from verified to guessed. The pattern is useful well beyond 3D.
MewCP vs Arcade: Comparing Actions Runtimes for AI Agents
A layer-by-layer comparison of MewCP and Arcade.dev, two enterprise actions runtimes that give AI agents an MCP gateway, a tool catalog, managed auth and governance, with deployment, compliance, pricing and clear advice on when each one fits.