node-connect

Diagnose OpenClaw node pairing failures across local, LAN, Tailnet, and public URL setups.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and resolves OpenClaw node connection and pairing failures across Android, iOS, and macOS companion apps, helping users recover from misconfigurations and network issues that block pairing.

Core Features & Use Cases

  • Canonical checks with openclaw qr --json and devices status to identify routing and authentication problems.
  • Guidance for common topologies: same machine, local LAN, Tailnet, and public URL scenarios.
  • Step-by-step root-cause analysis and recommended fixes to restore connectivity.

Quick Start

Run the diagnostic sequence and identify the correct gateway route (local LAN, Tailnet, or public URL) for the current OpenClaw node, then apply the appropriate fix.

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 node pairing failures when the QR setup code is not working?

OpenClaw node pairing failures when the QR setup code is not working are diagnosed by running openclaw qr --json to identify routing or authentication problems, then applying the recommended corrective action to restore connectivity across your companion apps.

How do I diagnose OpenClaw gateway connection issues on a Tailnet?

Diagnose OpenClaw gateway connection issues on a Tailnet by assessing gateway.tailscale and gateway.bind configurations via openclaw config commands, which isolate routing problems specific to Tailnet topologies and provide a targeted fix.

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

Your OpenClaw app reports a bootstrap token invalid or unauthorized error due to misconfigured gateway.remote.url or authentication settings, which can be identified and resolved by running openclaw devices status and assessing your gateway config.

Can I manually configure the host and port to resolve OpenClaw node connection problems?

Yes, you can manually configure the host and port to resolve OpenClaw node connection problems when QR pairing fails, using the diagnostic sequence to identify the correct gateway route and apply the appropriate manual host and port fix.

What is the best way to troubleshoot OpenClaw public URL connection failures?

The best way to troubleshoot OpenClaw public URL connection failures is to assess gateway.remote.url and related configurations via openclaw config commands, which evaluate public URL routing scenarios and provide a single recommended corrective action.