It grows without bound
Every new convention, edge case, and workaround gets appended. What started as a helpful guide becomes an unreadable wall of text.
mex gives engineering teams a shared, structured memory system for AI coding agents — with an admin panel to keep context aligned, validated, and current as your project grows.
Looking for the local open-source version? View on GitHubThe open-source version of mex runs locally on your machine. View the source and documentation on GitHub.
The problem
Most teams start with a single rules or instructions file per developer. It works at first — then quietly fragments collaboration and degrades AI output across the team.
Every new convention, edge case, and workaround gets appended. What started as a helpful guide becomes an unreadable wall of text.
The codebase evolves daily. Your instructions file does not. Agents end up following rules that no longer match reality.
Each developer maintains their own version. Context becomes inconsistent across machines, repos, and team members.
Sending the entire file with every request burns context window and budget — paying for outdated information repeatedly.
Over time, agents lose focus. Suggestions become generic, miss project nuance, and require more correction from you.
The solution
mex replaces scattered instructions files with a shared memory system your whole team works from. An admin panel gives leads visibility and control — so context stays organized, validated, and aligned as people, priorities, and code change.
The result: every developer's AI agents draw from the same trusted source, and your team spends less time correcting drift and more time shipping.
How it works
Four steps from scattered context to team-wide reliability — with an admin panel at the center.
Structure project knowledge into shared layers — conventions, architecture, priorities — instead of one file per developer.
mex continuously checks memory against your codebase so every teammate's agents work from context that is still true.
Review, update, and govern shared memory in one place. Team leads see what agents know and fix drift before it spreads.
As your team and codebase grow, mex keeps everyone working from the same trusted memory — week after week.
Who it's for
mex is designed for collaborative development — with an admin panel so leads can keep shared context honest and current.
Why we built mex
We started like most teams — everyone maintaining their own instructions file, agents drifting apart within weeks. Corrections piled up, context went stale, and nobody had a clear view of what our AI tools actually knew. We built mex so teams can share structured, validated memory — with an admin panel to keep it honest — instead of hoping individual rules files stay in sync. AI-assisted development should get better as your team grows, not harder.
The team version of mex — with shared memory and an admin panel — is available through our beta program. Request access for your team above.
The open-source version of mex runs locally on your machine. View the source and documentation on GitHub. It is MIT licensed and maintained at mex-memory/mex on GitHub.
Insights
Perspectives on context drift, team alignment, and building reliable AI workflows that last.
Agents, models, and IDEs get most of the attention. But without memory infrastructure, none of it scales past the first month.
Read moreWhen every developer has a slightly different version of the truth, AI output becomes inconsistent — and trust erodes fast.
Read moreThe instructions file that worked on day one becomes a liability by week four. Here is why — and what actually breaks.
Read moreShared memory, an admin panel, and agents that stay aligned — built for teams working on code together.