node-connect

Diagnose Kova node-to-gateway connectivity and pairing failures using openclaw commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and resolve Kova node-to-gateway connectivity and device pairing failures for Android, iOS, and macOS companion apps. It helps identify the single reachable route from a remote node to the gateway, verify what the gateway is advertising, and remediate pairing or authentication errors such as "pairing required", "unauthorized", or "bootstrap token invalid or expired".

Core Features & Use Cases

  • Topology-first diagnosis: Guides you to decide whether the setup is same-machine, same-LAN, Tailscale tailnet, or public URL and restricts fixes to that topology.
  • Canonical checks: Walks through exact commands and the meaning of prime outputs (openclaw qr --json, gateway.* config keys, openclaw devices list, openclaw nodes status, tailscale status).
  • Root-cause mapping and fixes: Maps common QR and token errors to concrete fixes (enable Tailscale Serve, set gateway.bind=lan, set plugins.entries.device-pair.config.publicUrl, regenerate setup codes, approve pending devices).
  • Fast heuristics and safe workflow: Provides quick heuristics to avoid common mistakes (don't switch routes prematurely, approve pending pairings before changing configs) and prescribes one concrete diagnosis + fix.

Quick Start

Diagnose a failing mobile pairing by running openclaw qr --json, checking openclaw devices list and gateway config values, confirming the advertised gatewayUrl and urlSource, and then report the single most likely root cause and one concrete 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 Kova app pairing failures when the bootstrap token is invalid or expired?

To fix Kova app pairing failures with invalid or expired bootstrap tokens, inspect the openclaw qr --json output and openclaw devices list to identify stale tokens, then regenerate setup codes and approve any pending devices.

Why does my Kova companion app say pairing required when connecting over Tailscale?

Kova companion apps show pairing required over Tailscale when the gateway route advertisement or auth values mismatch; check tailscale status and gateway config values to ensure Tailscale Serve is enabled and the advertised gatewayUrl is correct.

What's the best way to diagnose node-to-gateway connectivity issues across different network topologies?

The best way to diagnose node-to-gateway connectivity issues is to first determine your topology—same-machine, same-LAN, Tailscale tailnet, or public URL—then inspect openclaw qr --json and openclaw devices list to restrict fixes to that specific setup.

Does the Kova gateway support manual connections when QR setup codes fail?

Yes, the Kova gateway supports manual connections when QR setup codes fail; inspect gateway.* config keys and plugins.entries.device-pair.config.publicUrl to verify the advertised urlSource and apply the correct manual connect parameters.

How do I resolve unauthorized errors when pairing a mobile device to the Kova gateway?

To resolve unauthorized errors when pairing a mobile device to the Kova gateway, check openclaw devices list for pending pairings, approve them before changing configs, and verify gateway.bind=lan to ensure proper authentication across your network topology.

When should I not switch gateway routes while troubleshooting Kova pairing problems?

You should not switch gateway routes while troubleshooting Kova pairing problems until you have fully inspected openclaw nodes status and tailscale status, as prematurely changing routes can mask the actual root cause of route advertisement or auth mismatches.