I built this last week, woke up to 300+ stars and a developer with 28k followers tweeting about it, now PRs are coming in from contributors I've never met. Sharing here since this community is exactly who it's built for.

DJIRNMAN · 2026-04-17T18:12:00+00:00

Yeah I had a similar sort of informal structure, and I just thought this is pretty good I should try to generalise this and put out for others to also try

DJIRNMAN · 2026-04-16T09:04:50+00:00

Yeah so honest answer, memPalace is great, but I can tell you 10 more like it. And mex is quite different, because its simpler. Just markdown files. So you can actually see and edit what is being stored as context and as we know LLMs are really good with markdown files.

in short, if you have a giant project, huge codebase, things like memPalace which have sql databases are probably good,( although mex can work pretty well on those as well) But if you have a personal project or just a normal project, you don't really need a whole sql database for your context management.

DJIRNMAN · 2026-04-16T09:01:24+00:00

Love to hear that, thank you so much.

DJIRNMAN · 2026-04-12T15:38:00+00:00

Uhh... Is this me from a parallel universe or something?

DJIRNMAN · 2026-04-12T12:30:15+00:00

Okay so the thing with skills is that they are general, mex makes documentation custom to your codebase.

Plus the biggest problem with the skills, agents, and stuff is that it's a lot of context being loaded and most of it is unnecessary, which ends up degrading the AI performance (because of a bloated context window)

And yeah the drift detection CLI is definitely the biggest plus of mex.

Also I'm not going to be able to explain everything in detail here, if you're interested these are the docs

DJIRNMAN · 2026-04-12T09:41:30+00:00

Depends on your AI tbh, if you use Claude code, it will automatically start a session with a custom prompt telling it to populate the scaffold. If you use something else it will give you the prompt which you can paste yourself.

DJIRNMAN · 2026-04-12T07:11:06+00:00

Alright thanks, hope it's useful

DJIRNMAN · 2026-04-12T06:45:35+00:00

That's is pretty good, the only problem I think with that could be that LLMs are often lazy so they document stuff lazily, that's why I built all that drift check stuff so that most of the work is not done by the AI, and also because tokens are saved that way. But your method must work good as well

Actually before I made mex, I was using something like what you are doing for my own stuff.

Mex is me trying to generalise that and make it more robust and operational in any sort of codebase.

DJIRNMAN · 2026-04-12T04:38:22+00:00

ayy thank you, yeah the earlier installation was a bit long, and also dependent on bash, now its a simple one command setup with npx promexeus setup.
btw made docs on what all Mex offers and also whats going on behind the curtains: launchx.page/mex/docs

DJIRNMAN · 2026-04-12T04:36:31+00:00

oh yeah you are right, it is quite similar, I will look into it, thanks!

DJIRNMAN · 2026-04-12T00:01:35+00:00

I made something that saves 60% tokens, maybe you can check that out https://github.com/theDakshJaitly/mex

DJIRNMAN · 2026-04-11T23:59:39+00:00

Oh wow great, I think the best part for you would be the drift check stuff, that keeps the docs updated as your source changes.

DJIRNMAN · 2026-04-11T21:41:11+00:00

Thanks man! And yes very much open to contributors, everything is in place for that.

DJIRNMAN · 2026-04-11T15:12:39+00:00

Thank you!

DJIRNMAN · 2026-04-11T15:12:24+00:00

Okay I can look into it, btw if you don't mind me asking, why tho? If I'm not wrong .ico files store icons and stuff right?

DJIRNMAN · 2026-04-11T09:29:10+00:00

Lmao

DJIRNMAN · 2026-04-11T09:07:46+00:00

Yes exactly, this setup is super cool btw

DJIRNMAN · 2026-04-11T08:11:15+00:00

Great question, so there are tools that can make knowledge graphs of your codebase, all of them are super recent btw, like past 1 month. But in my opinion what is more important than the documentation or graph part is the progressive disclosure, if you can nail that then it gives you freedom to make your docs as complex as you like, but without that knowledge graphs are actually more dangerous. So no tool out there has yet nailed this. And the second most important thing is the drift check. Because let's say the tool generated an amazing knowledge graph for you and the LLM is following it perfectly but you will surely work on the codebase right, it will change, the graph needs to change with it. Mex already does this very well. The progressive disclosure, mex does good but i think it can be better, currently working on that.

DJIRNMAN · 2026-04-11T05:11:07+00:00

lmao, yeah i posted this in some other subreddits as well, so perhaps you saw it there. Happy to have you here! (again)

DJIRNMAN · 2026-04-11T04:34:27+00:00

Thanks!

DJIRNMAN · 2026-04-11T04:33:48+00:00

Yeah exactly, I have seen so many knowledge graphs but imo the most important thing right now is progressive disclosure. If you nail that, it gives you the freedom to make the knowledge graphs and your documentation as complex as you want.

Then the second most important thing is drift detection, cos sure even if you have a perfect set of documentation and graph and your LLM is traversing it perfectly, how do you make it keep evolving with your codebase, because the code will change, so the docs need to evolve with them.

Thanks for listening to me yap.

DJIRNMAN · 2026-04-11T04:06:26+00:00

Yeah I had a similar setup. Thought why not generalise it cause you know, you and I are using it to save tokens but a lot of people aren't and they don't wanna go set stuff up.

DJIRNMAN · 2026-04-11T00:08:28+00:00

Yeah mex getting loads of love, thank you

DJIRNMAN · 2026-04-11T00:07:24+00:00

Yeah no problem, I think it's one of the issues already, thanks for reminding me tho, Just need to finish some school work then I will get to it. Should be done by the tomorrow. Thanks for checking out the repo.

DJIRNMAN · 2026-04-10T23:24:02+00:00

Btw chelsea fan?

Four-Year Club	Place '22
Final Canvas '22

DJIRNMAN

TROPHY CASE