node-connect

Diagnose OpenClaw node connection failures by validating gateway routes and mapping error messages.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill node-connect-johnnywhitemike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-connect
Source: https://github.com/JOHNNYWHITEMIKE/openclaw/tree/main/openclaw/.openclaw/openclaw/skills/node-connect
Command: npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill node-connect-johnnywhitemike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose why OpenClaw nodes can’t reach the gateway for Android, iOS, or macOS companion apps, especially when pairing fails or the app reports authentication/bootstrap errors.

Core Features & Use Cases

  • Route discovery via QR payload: Determines the exact gateway endpoint the app should use by analyzing the setup-code/QR configuration output.
  • Topology-aware troubleshooting: Prevents mixing LAN, same-machine, tailnet, and public URL approaches by guiding checks based on the intended connection path.
  • Pairing/auth root-cause mapping: Interprets common failure messages (pairing required, unauthorized, bootstrap token invalid/expired) and links them to concrete configuration fixes.
  • Operational verification: Uses OpenClaw commands to inspect gateway mode/bind/auth/public URL, validate device pairing state, and confirm node status.

Quick Start

Run the Skill’s diagnostics by collecting the exact app error text and then execute the gateway and QR checks needed to identify which endpoint (gatewayUrl) the app will attempt to contact.

Frequently Asked Questions about node-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix OpenClaw pairing failures on iOS or Android?

OpenClaw pairing failures are fixed by validating the gateway route advertised in your QR setup code and mapping the specific app error to a configuration cause. You must inspect the QR JSON gatewayUrl and urlSource to select the correct topology-specific remediation.

Why does my OpenClaw companion app report an unauthorized or bootstrap token invalid error?

Unauthorized or invalid bootstrap token errors indicate a gateway configuration mismatch. You must run OpenClaw config and node status commands to verify your gateway mode, authentication state, and public URL against the expected connection topology.

How do I configure OpenClaw remote gateway routing over a Tailscale tailnet?

OpenClaw remote gateway routing over Tailscale requires verifying your tailscale state and checking the QR payload's urlSource to ensure the companion app targets the tailnet endpoint rather than a local LAN address.

What causes OpenClaw manual connect to fail when switching between LAN and public URL routing?

Manual connect failures occur when mixing LAN, same-machine, tailnet, and public URL routing approaches. You must execute OpenClaw gateway bind and public URL checks to isolate the advertised endpoint causing the topology mismatch.

Does OpenClaw node connection diagnostics work without a running Tailscale network?

OpenClaw node connection diagnostics work without Tailscale by focusing on LAN or public URL topologies instead. The Skill optionally verifies tailscale state only when remote tailnet routing is the intended connection path.