clawdio

What This Skill Does

Clawdio provides a robust, decentralized, and secure framework for peer-to-peer (P2P) communication specifically designed for AI agents. By implementing the Noise XX handshake and XChaCha20-Poly1305 encryption, it ensures that data exchanged between agents remains private and tamper-proof without the need for central relay servers. The skill enforces strong security postures through manual connection consent and human verification workflows, allowing agents to establish verified trust levels ('pending', 'accepted', and 'human-verified') while maintaining forward secrecy.

Installation

To integrate Clawdio into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/jameseball/jameseball-clawdio

Ensure you have the necessary dependencies installed by navigating to the project directory and running npm install && npx tsc. This will compile the TypeScript source and prepare the Clawdio runtime for your agent.

Use Cases

Clawdio is ideal for complex agent architectures. Common use cases include:

• Distributed Task Delegation: A master agent delegates specific sub-tasks to specialized agents running on different physical machines or cloud instances.
• Private Agent Clusters: Creating private, serverless networks where agents share sensitive datasets or insights without external exposure.
• Secure Remote Management: Controlling remote agents through an authenticated P2P pipe that bypasses the need for open firewall ports or third-party web sockets.
• Identity Verification Chains: Building high-trust multi-agent systems where human oversight is required for sensitive operations, confirmed via fingerprint/verification code matching.

Example Prompts

1. "Clawdio, initialize a new connection node on port 9095 and wait for the inbound request from the analytics sub-agent; confirm once the peer is accepted."
2. "Establish a secure P2P channel with the remote agent at the provided connection string and verify its identity using the 6-word code provided by the human operator."
3. "List all current active peers in my Clawdio network and provide their current trust status (pending, accepted, or human-verified)."

Tips & Limitations

• Persistence: Always utilize the identityPath configuration during node creation. Without this, your keys will reset on restart, forcing you to re-authenticate with all your peers.
• Networking: Since this is true P2P, ensure that firewalls allow traffic on the ports you specify for your Clawdio nodes.
• Human Verification: For sensitive tasks, never skip the getVerificationCode step. It is the only way to mathematically guarantee you are not talking to a malicious agent spoofing a known identity.
• Sub-Agents: Always encapsulate your Clawdio logic within a sub-agent pattern to keep your main agent's memory footprint clean and to isolate network-related error handling.