node-connect

Diagnose and fix node pairing failures with the OpenClaw gateway.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Node connection and pairing can fail across Android, iOS, and macOS companions, leaving devices unable to reach the gateway or authenticate.

Core Features & Use Cases

  • Diagnose routing and pairing failures between a node and gateway.
  • Recommend fixes for common scenarios: local network, VPN/Tailscale, or public URL configurations.
  • Provide actionable steps to re-pair devices and restore connectivity.

Quick Start

Run a diagnostic on the affected node to identify the most likely route and re-establish pairing.

Frequently Asked Questions about node-connect

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

FAQPage Schema
How do I fix node connection and pairing failures with the OpenClaw gateway?

To fix node connection and pairing failures, diagnose the affected node to identify routing issues and verify gateway configurations, then follow deterministic steps to re-pair the device and restore connectivity.

Why does my Android companion fail to reach the gateway over Tailscale?

Android companions fail to reach the gateway over Tailscale when routing or gateway configurations are incorrect. Run a diagnostic to verify the gateway.remote.url and plugin-pair settings, then re-pair the device.

Does this diagnose local Wi-Fi and public URL setups for macOS companions?

Yes, this diagnoses macOS companions across local Wi-Fi, VPN/Tailscale, and public URL setups, verifying gateway.bind and gateway.remote.url configurations to identify and fix connection failures.

What is the best way to re-pair a device using a QR or setup code?

The best way to re-pair a device using a QR or setup code is to run a diagnostic on the affected node, verify the plugin-pair configurations, and follow the guided re-pairing steps to restore connectivity.

When should I manually verify gateway.bind and gateway.remote.url for connectivity?

You should manually verify gateway.bind and gateway.remote.url when a node diagnostic identifies configuration mismatches, particularly across local network, Tailscale, or public URL setups causing pairing failures.