Set up mex agent memory (AGENTS.md + .mex/ scaffold)#84
Merged
Conversation
Rename CLAUDE.md to AGENTS.md as the canonical agent instructions file, with CLAUDE.md becoming a symlink to it. Add a populated mex scaffold (.mex/) with context files, task patterns, and a session router, and wire the GROW loop into AGENTS.md so agents keep the scaffold updated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Sets up mex — persistent, structured project memory for AI coding agents — and reorganizes the agent instruction files:
CLAUDE.md→AGENTS.md: the canonical agent instructions file is now the tool-agnosticAGENTS.md;CLAUDE.mdis a symlink to it, so Claude Code and other tools read the same content..mex/scaffold, fully populated from the codebase (not template boilerplate):ROUTER.md— session bootstrap: current project state, routing table, behavioural contractcontext/— architecture, stack, conventions, decisions (dated from git history), setup, plus two domain files:reports.md(v1/v2/v3 schemas and the DynamoDB lookup chain) andauth.md(launch-token flow)patterns/— five task runbooks: add-report-endpoint, add-db-query, generate-pdf, debug-local-startup, deployAGENTS.mdso agents update the scaffold after meaningful work.claudeandcodexas AI tools.Why
Session-to-session agent context previously lived in one flat CLAUDE.md. mex routes agents to only the context relevant to their task, keeps project state current, and its CLI (
mex check) catches documentation drift against the real codebase with zero tokens.mex checkon this branch: 100/100.Notes
🤖 Generated with Claude Code