node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.
npx skills add SafeAI-Lab-X/ClawKeeper --skill node-connect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Node Connect Goal: find the one real route from node -> gateway, verify OpenClaw is advertising that route, then fix pairing/auth. ## Topology first Decide which case you are in before proposing fixes: - same machine / emulator / USB tunnel - same LAN / local Wi-Fi - same Tailscale tailnet - public URL / reverse proxy Do not mix them. - Local Wi-Fi problem: do not switch to Tailscale unless remote access is actually needed. - VPS / remote gateway problem: do not keep debugging `localhost` or LAN IPs. ## If ambiguous, ask first If the setup is unclear or the failure report is vague, ask short clarifying questions before diagnosing. Ask for: - which route they intend: same machine, same LAN, Tailscale tailnet, or public URL - whether they used QR/setup code or manual host/port - the exact app text/status/error, quoted exactly if possible - whether `openclaw devices list` shows a pending pairing request Do not guess from `can't connect`. ## Canonical checks Prefer `openclaw qr --json`. It uses the same setup-code payload Android scans. ```bash openclaw config get gateway.mode openclaw config get gateway.bind openclaw config get gateway.tailscale.mode openclaw config get gateway.remo
- Topology first
- If ambiguous, ask first
- Canonical checks
- Read the result, not guesses
- Root-cause map
- Fast heuristics
- Fix style
openclaw config get gateway.mode openclaw config get gateway.bind openclaw config get gateway.tailscale.mode openclaw config get gateway.remote.url openclaw config get gateway.auth.mode openclaw config get gateway.auth.allowTailscale openclaw config get plugins.entries.device-pair.config.publicUrl openclaw qr --json openclaw devices list openclaw nodes status
What does the node-connect skill do?
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.
How do I install it?
Run `npx skills add SafeAI-Lab-X/ClawKeeper --skill node-connect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From SafeAI-Lab-X/ClawKeeper, a repository with 1,027 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.