Coordinating Multiple AI Agents: Discord, Cron Jobs, Hierarchy

Problem: Multiple Agents Without Coordination

The developer runs three OpenClaw agents: two on Claude Max and one on OpenAI. Initially, these agents operated independently without awareness of each other, requiring manual coordination that was inefficient.

Paperclip was tried for coordination but proved expensive due to frequent heartbeats that consumed tokens even when no work was happening. Telegram and Slack were also attempted but failed to provide reliable message visibility between agents.

Solution: Discord as Shared Workspace

The working solution was Discord. A server was created with topic-specific channels: development, marketing, and finance. All three agents were added to the same channels where they can:

Read each other's messages
@ mention each other
Hand off tasks between agents

Tasks are simply dropped in the relevant channel, and the most appropriate agent picks them up. Discord serves as their "shared office" and creates a living log of all activity.

Cost Control: Replacing Heartbeats with Cron

Instead of using a global heartbeat system that fires every few seconds, each agent now runs on its own cron schedule. Agents only wake up when there's actual work to do, eliminating the cost of idle "breathing" cycles.

Agent Hierarchy and Model Selection

To prevent chaos, a clear chain of command was established:

Marusya: Runs on Claude Opus, acts as project lead. Breaks down projects, writes guidelines, and delegates work.
Marsel: Runs on Claude Sonnet, handles execution tasks.
Makar: Runs on Codex, handles heavy technical work.

This structure follows "one leads, two execute" principle. The developer specifically recommends mixing models based on their strengths rather than seeking a single "best" model.

Technical Setup Details

Two agents run on the same Mac machine. One is installed as the standard OpenClaw instance, while the second runs as a separate instance with a custom alias. In terminal, agents are invoked by their custom names instead of "openclaw."

Results: From Tasks to Projects

With coordinated agents, the developer shifted from thinking about individual tasks to complete projects. As a test case, agents built a content platform overnight while the developer slept. The resulting application included: