Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Communicate with other OpenClaw agents on your local network. Use when you need to ask another agent a question (sync), delegate a task (async), or check if...
Communicate with other OpenClaw agents on your local network. Use when you need to ask another agent a question (sync), delegate a task (async), or check if...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Talk to other OpenClaw agents on your LAN.
Copy config/peers.example.json to config/peers.json Fill in peer hostnames, ports, and tokens Ensure target agents have the required APIs enabled (see below) Set up a secure transport (see Network Transport below)
For sync ask (chat completions): // Target agent's openclaw.json — keep bind as "loopback"! { "gateway": { "http": { "endpoints": { "chatCompletions": { "enabled": true } } } } } ⚠️ Do NOT set gateway.bind to "lan" — OpenClaw will refuse to start if the gateway is exposed on a non-loopback address without TLS. Use a secure transport instead (see below). For async delegate (webhooks): { "hooks": { "enabled": true, "token": "a-secure-shared-secret" } }
OpenClaw gateways default to bind: loopback and will not start with plaintext on non-loopback addresses. You need a secure transport layer for cross-host communication: ApproachComplexityBest ForSSH Tunnel ⭐LowHome LANs, simple setupsReverse Proxy (TLS)MediumEnvironments with existing Caddy/nginxTailscale ServeMediumMulti-site or remote agents For simple LANs, SSH tunneling is recommended. Both gateways stay on loopback, the SSH tunnel provides encryption, and no gateway config changes are needed.
Forward a local port to the remote agent's loopback gateway: ssh -N -L 18790:127.0.0.1:18790 user@remote-agent-host Then in peers.json, point the peer to 127.0.0.1:18790 (the local tunnel endpoint). For persistence, use a systemd user service with Restart=always. See the full setup guide in docs/setup.md.
scripts/lobsterlan.sh ask scotty "What is the CPU temperature?" Use for quick questions where you need the answer now.
scripts/lobsterlan.sh delegate scotty "Generate 5 zen wallpapers and push to the file share" Use for long-running tasks. The peer processes independently.
scripts/lobsterlan.sh status scotty
scripts/lobsterlan.sh peers
Run via exec tool: cd ~/.openclaw/workspace/skills/lobsterlan && scripts/lobsterlan.sh ask scotty "status report"
Three layers protect communication: Network: LAN-only (firewall blocks external access to gateway port) Gateway token: Bearer auth on every request Agent ID header (optional): X-LobsterLAN-Agent sent with self-ID The gateway token is the real security boundary. The agent ID header is defense-in-depth for environments where you want explicit identity verification.
LOBSTERLAN_CONFIG — path to peers.json (default: ../config/peers.json relative to script)
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.