91–95 of 95 posts
The better way to do this is give them each an inbox and outbox folder and a user account on a Unix machine. They can write to their outbox, have it be sent to the other's inbox. A watcher can watch for new messages in the inbox and trigger the other agent to read it. You can have the thread Id of the messages correspond to the session id. We don't need to reinvent things that Unix provides.
Earlier quoted context omitted.
I am not very well versed in these kind of tools. How does it compare with something like Hindsight MCP? How 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.
Earlier quoted context omitted.
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
I am not very well versed in these kind of tools. How does it compare with something like Hindsight MCP? How 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.