Cheers — quite a bit more work going into that presently and extensive testing to back it up. Early finding: auto-extracted memory is no better than a hand-written doc. Human curation is the lever. Numbers at the top of the mori README.
It isn't the memory store.. that's entirely separate. But it complements the memory store by allowing the agents to pub / sub notifications. Has its uses!
Yes, the multi-agent governance takes a lot of solving.. thus far I've gotten Hermes writing to the same memory store that Claude code, antigravity, cursor, etc can all contribute, pull from, but it's taken a whole separate layer of governance.
Agents that can write to shared memory are powerful. Agents that can write to shared memory without oversight are a liability. Mori has the governance layer - https://github.com/fjwood69/mori
how to capture, what to capture, when to capture it.. where to put it.. how to make it 'useful'.. how to reinject it or make it accessible
the harness makers may well come up with better means than flat files, but there are loads of folks out there working across different harnesses and in teams, and there's very little that works in that respect.
about six weeks.. Pushed a v1.0 product with a huge list of v2.x enhancements and features inbound.
to your point about asking Codex.. that's my /consult feature. spin out the current context in any number of ways to ask for advice.. on a plan, on a specific architectural decision, on a security basis.. I use it all the time as a check on everything Claude Code proposes.
So I solved this by using NATS and letting each agent pub / sub to the shared message bus.. simple binary you can run anywhere and it's highly useful! Part of a broader tool I created - https://github.com/fjwood69/mori
Whitepaper - https://moriapp.dev/pbgf