What problem does it solve? Mobile and desktop nodes fail to connect to an OpenClaw gateway for many reasons—loopback-only binding, wrong network route, expired setup codes, or unapproved pairing requests—and vague errors like "can't connect" make root causes hard to find. ## Core Features & Use Cases - Topology-First Diagnosis: Classifies the setup as same machine, same LAN, Tailscale tailnet, or public URL before proposing any fix, avoiding mixed-route debugging. - Canonical Verification Commands: Uses openclaw qr --json, openclaw devices list, and config getters to read the actual advertised gateway URL and its source instead of guessing. - Root-Cause Mapping: Maps specific symptoms (loopback binding, invalid bootstrap token, unauthorized, pending pairing) to concrete fixes like enabling Tailscale Serve or approving a device request. - Use Case: A user's Android phone shows "pairing required" after scanning a QR code; the Skill identifies that the network route already works and directs the user to approve the pending request via openclaw devices approve <requestId>. ## Quick Start Diagnose why my Android phone cannot connect to my OpenClaw gateway after scanning the QR setup code.
