node-connect

Diagnose and fix OpenClaw node pairing failures across Android, iOS, and macOS.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw node connection and pairing can fail due to QR/setup issues, local network constraints, or remote gateway misconfigurations. When QR codes or manual host/port setups fail, apps on Android, iOS, or macOS cannot establish a stable gateway path, leading to authentication errors or inaccessible tailnets.

Core Features & Use Cases

  • Diagnose the active gateway route and verify the node advertises the expected path across local, VPN, tailscale, and public URL scenarios.
  • Guide canonical checks, collect status information, and provide concrete remediation steps to repair pairing and gateway configuration.
  • Use Case: trouble-shoot a device with a pending pairing request or a loopback gateway to ensure successful remote access.

Quick Start

Run the node-connect flow to diagnose the active gateway route and repair pairing on Android, iOS, or macOS.

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 doesn't work?

To fix OpenClaw node pairing failures when QR setup codes fail, diagnose the active gateway route to verify the node advertises the expected path, validate manual host/port configurations, and approve any pending device requests until pairing succeeds.

Why does my OpenClaw node connect on local Wi-Fi but fail over Tailscale or VPS?

OpenClaw node connections work on local Wi-Fi but fail over Tailscale or VPS due to remote gateway misconfigurations, requiring you to read the gateway config and validate routes to repair the public URL or tailnet access path.

What does a 'bootstrap token invalid or expired' error mean during node pairing?

A 'bootstrap token invalid or expired' error during node pairing indicates an authentication failure in the gateway path, requiring canonical checks and gateway configuration validation to re-establish a stable connection.

How do I resolve 'gateway.bind' or 'gateway.remote.url' errors on my OpenClaw node?

Resolve 'gateway.bind' or 'gateway.remote.url' errors on your OpenClaw node by reading the gateway config, enforcing canonical checks, and validating the advertised routes to ensure proper local, VPN, or public URL connectivity.

Can I troubleshoot OpenClaw pairing issues across Android, iOS, and macOS companion apps?

Yes, you can troubleshoot OpenClaw pairing issues across Android, iOS, and macOS companion apps by diagnosing the active gateway route and guiding canonical checks to repair pairing and gateway configuration for each specific platform.

What should I do if my OpenClaw app shows a 'pairing required' or 'unauthorized' error?

If your OpenClaw app shows a 'pairing required' or 'unauthorized' error, you need to validate the gateway routes, check the plugins.entries.device-pair.config.publicUrl setting, and approve the pending device to complete the pairing process.