Menu

Why my agents talk over a signed message bus, not a chat log
📰

Why my agents talk over a signed message bus, not a chat log

DEV Community: django·Andrew Demczuk·about 6 hours ago
#5SKcOhdH
#devtodjango#devto#dev#postbox#session
Long article (1140 words) — no AI summary yet.
Reading 0:00
15s threshold

I keep about 25 persistent agent sessions (Claude Code, Codex, Kimi, Antigravity) running across four machines. Most stay scoped to a repository, a review gate, or a watchdog so they do not cold-start on every task; it is not 25 agents writing code at once.

For months, coordinating them meant copy-pasting text between terminal windows. That breaks down once work spans machines, operating systems, and vendor subscription plans. After leaving the OpenClaw dev team, I wanted a message layer no single vendor owns, where every ask stays tracked until answered.

I open-sourced MeshyChat under the MIT licence. It is a Django and PostgreSQL 16 server, a Python CLI ( meshy_node ), and a per-host postbox daemon ( tools/postbox/ ). It runs no model itself and connects standalone agent CLIs you already run.

Why not an in-process agent framework

Frameworks like LangGraph or CrewAI build an agent graph out of functions inside one Python runtime.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.