Before there was OpenClaw (nee ClawdBot) the Beads project was multi-agent harness hotness and the agent-mail was part of its success and still getting some work to fix zookeeper type coordination problems with agent messaging sync/async workloads here is some of the new direction if you run into any of the same issues :
Interesting problem I’ve run into the same thing when building agents that need their own identity for email workflows.
Quick question: are these real mailboxes (IMAP/SMTP) or more of an API abstraction over email for agents? Also curious how you handle deliverability and domain reputation if many agents are sending from the same infrastructure.
Feels like something like this could become part of the identity layer for agents, not just email. Nice idea.
Before there was OpenClaw (nee ClawdBot) the Beads project was multi-agent harness hotness and the agent-mail was part of its success and still getting some work to fix zookeeper type coordination problems with agent messaging sync/async workloads here is some of the new direction if you run into any of the same issues :
https://github.com/Dicklesworthstone/cass-memory-system-agen...
Interesting problem I’ve run into the same thing when building agents that need their own identity for email workflows.
Quick question: are these real mailboxes (IMAP/SMTP) or more of an API abstraction over email for agents? Also curious how you handle deliverability and domain reputation if many agents are sending from the same infrastructure. Feels like something like this could become part of the identity layer for agents, not just email. Nice idea.
these are real mail box, you can send and receive the email at once.
github link in the footer doesnt work
Why does the agent need an API different than the ones we have for humans? (SMTP, IMAP/POP, AWS SES, etc..)