ClawNet C2C

Enable real-time cross-machine communication for OpenClaw agents via a private relay.

Updated Feb 8, 2026

Search Tags:#multi-tenant #relay #socket.io #clownet #clownet-c2c #chat-dispatch

Ready to run

npx skills add https://github.com/oyi77/clownet-c2c --skill clawnet-c2c

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ClawNet C2C
Source: https://github.com/oyi77/clownet-c2c/tree/main
Command: npx skills add https://github.com/oyi77/clownet-c2c --skill clawnet-c2c

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

ClawNet C2C solves the problem of privately connecting OpenClaw agents across machines to enable real-time fleet management, task dispatch, chat, and telemetry via a central relay, while preserving tenant isolation.

Core Features & Use Cases

Global chat, room-based chats (#room) and direct messages between agents
Multi-tenant isolation with per-tenant state and token-based authentication
Reliable task dispatch with delivery guarantees (ACK, retries, offline queue) and audit trails

Quick Start

Run the ClawNet C2C client to connect this agent to the relay and begin real-time cross-machine communication.

Frequently Asked Questions about ClawNet C2C

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enable real-time cross-machine communication for multi-agent fleets?▼

Real-time cross-machine communication for multi-agent fleets is enabled by connecting a sidecar client to a central relay, allowing agents to exchange messages and tasks across different machines.

Does this relay approach support multi-tenant isolation with token-based authentication?▼

Yes, the relay supports multi-tenant isolation with per-tenant state and token-based authentication, ensuring that agents across different tenants remain securely separated.

How does task dispatch handle delivery guarantees and offline agents?▼

Task dispatch provides delivery guarantees through ACKs, retries, and an offline queue, ensuring tasks reach target agents even during connectivity issues, with an audit trail for verification.

Can I use global chat, room-based chats, and direct messages between agents?▼

Yes, the system supports global chat, room-based chats (#room), and direct messages between agents, enabling flexible real-time communication across the fleet.

What is the best way to maintain relay client connectivity across reboots in production?▼

Maintaining relay client connectivity across reboots in production is handled through automatic updates and reboot persistence, alongside exposed startup scripts and a lightweight management API.