Fleet Comm

What This Skill Does

The Fleet Comm skill is a robust, lightweight multi-agent communication system designed for OpenClaw users running distributed fleets across multiple machines. It acts as an orchestration layer, allowing separate OpenClaw instances to share information, delegate tasks, and maintain synchronicity. At its core, it consists of a centralized HTTP message bus that acts as a post office for your agents, allowing them to route messages to specific nodes or broadcast commands fleet-wide.

Installation

To integrate this into your environment, use the OpenClaw hub command: clawhub install openclaw/skills/skills/dagangtj/fleet-comm

Once installed, you must designate a coordinator node to host the message bus using node fleet-comm/fleet_bus.js. Ensure that the FLEET_BUS_URL and FLEET_NODE_ID environment variables are correctly configured on all participating machines so that agents know how to reach the central bus.

Use Cases

This skill is essential for users moving beyond a single-machine setup. Common use cases include:

• Distributed Task Delegation: If you have one machine specialized for high-compute tasks and another for web crawling, Fleet Comm allows the crawler to signal the high-compute node to begin processing data.
• Fleet Coordination: Managing synchronized actions across diverse hardware, such as running a security sweep across a Mac, a WSL2 instance, and a dedicated Windows server simultaneously.
• Real-Time Alerting: Pushing notifications from a monitoring node to all other nodes in the fleet when a system or data threshold is met.

Example Prompts

1. "Fleet Comm, broadcast to all nodes: Initiate system update check and report back versions."
2. "Send a task message to node 02: Perform data extraction on the latest financial set and store locally."
3. "Check the current status of the fleet bus to ensure all nodes are connected and responding."

Tips & Limitations

• Networking: The system relies on network connectivity between nodes. In heterogeneous environments (e.g., local machines, WSL2, cloud servers), ensure that firewalls allow traffic on the selected port (default 18800).
• Security: In its current Free iteration, messages are transmitted in cleartext. Do not send sensitive credentials or private keys through the bus. For secure environments, use a private network overlay like Tailscale.
• Scalability: While highly performant for task signaling, this is a message-passing system, not a data streaming service. Keep messages concise to maintain fleet agility.