a2a-setup
Install and configure the Claw Crony A2A Gateway plugin for cross-server agent communication. Use when: (1) setting up A2A between two or more OpenClaw instances, (2) user says 'configure A2A', 'set up A2A gateway', 'connect two OpenClaw servers', 'agent-to-agent communication', (3) adding a new A2A peer to an existing setup. Covers: plugin installation, Agent Card configuration, security tokens, peer registration, network setup (Tailscale/LAN), TOOLS.md template for agent awareness, and end-to-end verification.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/ccccl8/claw-cronyWhat This Skill Does
The a2a-setup skill allows you to configure the Claw Crony A2A Gateway, a critical component for enabling decentralized communication between disparate OpenClaw server instances. By implementing the A2A v0.3.0 protocol, this skill bridges the gap between isolated agents, allowing them to route messages, share capabilities, and perform collaborative tasks across network boundaries. It automates the complex configuration of JSON-RPC endpoints, secure bearer authentication, and agent discovery mechanisms, ensuring that your OpenClaw ecosystem can scale horizontally by connecting multiple independent servers.
Installation
Installation is a multi-step process that requires environment awareness. First, navigate to your OpenClaw workspace plugins directory and clone the claw-crony repository using git. After installing production dependencies via npm install --production, you must register the plugin in your OpenClaw configuration. Use openclaw config set plugins.allow to append claw-crony to your existing plugins list and define the plugin's absolute load path. Next, configure the Agent Card, which acts as the identity card for your agent, defining its name, description, and the reachable endpoint. Finally, establish server binding, generate a secure 24-character hex token for inbound bearer authentication, and define routing defaults.
Use Cases
- Linking an internal data-processing server with a public-facing task coordinator.
- Implementing a multi-region agent architecture for redundancy and geographic latency reduction.
- Integrating legacy OpenClaw setups with newer, specialized agent domains.
- Enabling private cross-server communication over secure tunnels like Tailscale.
Example Prompts
- "Configure A2A gateway for this server and set up an agent card named 'research-node'."
- "I need to connect two OpenClaw servers; help me generate the security tokens and register the peers for A2A communication."
- "Update my agent-to-agent communication settings to use a new Tailscale IP for the gateway."
Tips & Limitations
Always ensure you use absolute paths when registering the plugin in plugins.load.paths to avoid initialization errors. Be careful not to overwrite your existing plugins array when updating the configuration. When setting up agentCard.url versus agentCardUrl, remember that the former is for inbound messaging while the latter is for outbound peer discovery. Finally, ensure both servers share the security token generated during the setup phase; communication will fail if the bearer tokens do not match.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-ccccl8-claw-crony": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, file-write, file-read