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
replyI am not very well versed in these kind of tools. How does it compare with something like Hindsight MCP?
replyHow do you make the agents actually use the tool? That has been my main problem with most mcp and tools. The agents know about them but don't use them unless reminded to.
https://en.wikipedia.org/wiki/NATS_Messaging is for real-time communication, so I would not use it as a substitute for a memory store.
reply[dead]
replythanks for sharing dude. How long did this take you?
replyabout six weeks.. Pushed a v1.0 product with a huge list of v2.x enhancements and features inbound.
replyto 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.
any / all feedback most welcome.
fw
I added a chat tool to https://github.com/rcarmo/piclaw, so any active session can chat to each other, regardless of what model they run. It's led to interesting outcomes: https://x.com/rcarmo/status/2054185558402904338?s=20
replyDoes it not turn into a never-ending snowball? Do they eventually agree on something?
reply