The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
npx ecc-install --profile fullFair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
npx n8nAn open-source AI agent that brings the power of Gemini directly into your terminal.
npx @google/gemini-cli
The agent starts with a tiny auto-loaded file. That file points to ROUTER.md, and the router loads only the context needed for the current task. After meaningful work, the GROW step updates project state, decisions, and task patterns so the scaffold becomes more useful over time.
Editable source: docs/diagrams/context-routing.excalidraw
Shows active maintenance signals
Carries strong trust indicators from repository metadata
1148 GitHub stars recorded
The npm package is named mex-agent because mex was already taken. The CLI command is still mex.
npx mex-agent setup
Setup creates the .mex/ scaffold, asks which AI tool you use, pre-scans your codebase, and generates a targeted prompt to populate the memory files. It takes about five minutes.
At the end of setup, you can install mex globally:
mex check # drift score
mex sync # fix drift
If you skip global install, use npx:
npx mex-agent check
npx mex-agent sync
Install globally later at any time:
npm install -g mex-agent
The recommended npx mex-agent setup flow runs in any terminal (Command Prompt, PowerShell, or WSL) and does not need bash, so most Windows users do not have to think about this section.
Windows users (legacy
setup.shflow): Run all commands inside WSL or Git Bash. Do not mix environments.
If you previously installed via the legacy setup.sh script, building inside WSL and then running the CLI from a native Windows terminal causes "module not found" errors because node_modules and path resolution differ between the two filesystems. Run install, build, and CLI commands inside the same environment: either entirely in WSL / Git Bash, or entirely in native Windows via npx mex-agent.
See issue #10 for context.
Optional settings live in .mex/config.json. Missing values fall back to defaults.
{
"staleness": {
"warnDays": 30,
"errorDays": 90,
"warnCommits": 50,
"errorCommits": 200
},
"heartbeat": {
"staleDays": 7,
"memoryCleanupDays": 7,
"dailyMemoryRetentionDays": 14
},
"watch": {
"intervalMinutes": 30
}
}