openclaw-diagnose

スター3

フォーク1

更新日2026年4月4日 07:21

Diagnose and fix OpenClaw gateway and node host issues. Use when openclaw services have warnings, connection failures, pairing errors, or port conflicts.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

soulmachine

soulmachine/skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

OpenClaw Diagnose

When the user asks you to diagnose or fix OpenClaw gateway/node issues, follow this structured investigation.

Step 1: Gather status

Run these in parallel:

openclaw gateway status
openclaw node status
openclaw nodes status
openclaw nodes pending

Step 2: Analyze warnings

Look for these common issues:

Multiple gateway-like services detected

Check if both ai.openclaw.gateway and ai.openclaw.node are registered as LaunchAgents
Use launchctl print gui/$(id -u)/<label> to inspect each service
Use lsof -iTCP:<port> -sTCP:LISTEN -P to confirm which process owns the port
The gateway listens on the port; the node host connects to the gateway on that port — they do NOT conflict

Pairing required errors

Check ~/.openclaw/logs/node.err.log for pairing required or ECONNREFUSED
If the node shows "pairing required", run openclaw nodes pending to find the pending request
Approve with: openclaw nodes approve <requestId>
Pairing requests expire quickly — if approval fails with "unknown requestId", restart the node (openclaw node restart) and immediately re-check pending + approve

ECONNREFUSED errors

The gateway may not be running yet when the node starts
Check if gateway is listening: lsof -iTCP:<port> -sTCP:LISTEN -P
If gateway is down: openclaw gateway restart
The node has KeepAlive: true so it will automatically reconnect once the gateway is up

Step 3: Verify fix

After taking corrective action, confirm health:

openclaw nodes status    # Should show: paired · connected
openclaw nodes pending   # Should show: No pending pairing requests
tail -5 ~/.openclaw/logs/node.err.log  # Check for new errors

Key architecture notes

Gateway (ai.openclaw.gateway): WebSocket server that listens on a port (default 18789)
Node host (ai.openclaw.node): Client that connects to the gateway via WebSocket to register capabilities (browser, system commands)
The --host and --port flags on openclaw node run specify the gateway address to connect to, not a port to bind
One gateway supports multiple nodes — running both on the same machine is the normal setup
Node plist is at ~/Library/LaunchAgents/ai.openclaw.node.plist
Gateway plist is at ~/Library/LaunchAgents/ai.openclaw.gateway.plist
Node logs: ~/.openclaw/logs/node.log and ~/.openclaw/logs/node.err.log

このリポジトリの他の Skills

同じリポジトリ

ssh-claude-auth

soulmachine/skills

Fix Claude Code appearing logged-out over SSH on a headless macOS machine — its credentials sit in the login keychain, which stays locked in SSH/headless sessions. Offers two fixes and asks the user to choose: a keychain-free long-lived OAuth token (recommended), or auto-unlocking the login keychain with a stored password. Use when Claude Code shows unauthenticated over SSH on a Mac, when setting up a Mac mini or headless Mac for remote/CI Claude Code use, or when `security show-keychain-info` reports the login keychain locked.

2026-07-173

affix-domains

soulmachine/skills

Attach popular brand prefixes/suffixes to a seed word and check each `.com` via Verisign RDAP. Use when the user names a word and asks for prefix/suffix `.com` variants, or wants domains generated by adding endings like -ly/-ify/-hub or beginnings like open-/get-/go-.

2026-07-143

chrome-cdp-setup

soulmachine/skills

Set up Google Chrome on macOS to always launch with the Chrome DevTools Protocol enabled (127.0.0.1:9222) via a Dock launcher app, so local AI agents (Playwright, Puppeteer, browser-use, OpenClaw) can drive the real logged-in browser. Use when the user wants to enable a CDP/remote-debugging port for Chrome, connect an agent to Chrome, test a CDP connection, or troubleshoot/revert an existing Chrome-CDP Dock setup.

2026-07-133

mac-mini-as-headless-server

soulmachine/skills

Use when setting up a Mac (especially Mac Mini or Apple Silicon Mac Studio) for unattended 24/7 server operation, headless use, or remote-only access. Covers sleep prevention, screen saver, Wake-on-LAN, auto-restart, App Nap, SSH enablement, and — on Apple Silicon — a caffeinate LaunchDaemon that stops the headless display from parking (physical panel and VNC/screen-share going black even with displaysleep=0). Targets macOS 15 (Sequoia) and later.

2026-07-083

build-stealth-rustdesk

soulmachine/skills

Build a patched, fully-stealth RustDesk.app from source on Apple Silicon, from a maintained private fork — no menu-bar icon, no Dock icon, no on-screen CM panel compiled in, remote keyboard still works, codesigned and ready to deploy. Use when building or version-bumping the stealth RustDesk binary; deploy the result with the deploy-stealth-rustdesk skill.

2026-07-043

deploy-stealth-rustdesk

soulmachine/skills

Deploy a prebuilt stealth-patched RustDesk.app as an unattended macOS LaunchAgent service — no Dock icon, no menu-bar icon, no on-screen CM panel, remote keyboard still works, survives reboot with nobody logged in. Use when installing a stealth RustDesk on a target Mac; build the app first with the build-stealth-rustdesk skill.

2026-07-043

OpenClaw Diagnose

When the user asks you to diagnose or fix OpenClaw gateway/node issues, follow this structured investigation.

Step 1: Gather status

Run these in parallel:

openclaw gateway status openclaw node status openclaw nodes status openclaw nodes pending

Step 2: Analyze warnings

Look for these common issues:

Multiple gateway-like services detected

Check if both ai.openclaw.gateway and ai.openclaw.node are registered as LaunchAgents

Use launchctl print gui/$(id -u)/<label> to inspect each service

Use lsof -iTCP:<port> -sTCP:LISTEN -P to confirm which process owns the port

The gateway listens on the port; the node host connects to the gateway on that port — they do NOT conflict

Pairing required errors

Check ~/.openclaw/logs/node.err.log for pairing required or ECONNREFUSED

If the node shows "pairing required", run openclaw nodes pending to find the pending request

Approve with: openclaw nodes approve <requestId>

Pairing requests expire quickly — if approval fails with "unknown requestId", restart the node (openclaw node restart) and immediately re-check pending + approve

ECONNREFUSED errors

The gateway may not be running yet when the node starts

Check if gateway is listening: lsof -iTCP:<port> -sTCP:LISTEN -P

If gateway is down: openclaw gateway restart

The node has KeepAlive: true so it will automatically reconnect once the gateway is up

Step 3: Verify fix

After taking corrective action, confirm health:

openclaw nodes status # Should show: paired · connected openclaw nodes pending # Should show: No pending pairing requests tail -5 ~/.openclaw/logs/node.err.log # Check for new errors

Key architecture notes

Gateway (ai.openclaw.gateway): WebSocket server that listens on a port (default 18789)

Node host (ai.openclaw.node): Client that connects to the gateway via WebSocket to register capabilities (browser, system commands)

The --host and --port flags on openclaw node run specify the gateway address to connect to, not a port to bind

One gateway supports multiple nodes — running both on the same machine is the normal setup

Node plist is at ~/Library/LaunchAgents/ai.openclaw.node.plist

Gateway plist is at ~/Library/LaunchAgents/ai.openclaw.gateway.plist

Node logs: ~/.openclaw/logs/node.log and ~/.openclaw/logs/node.err.log

name	openclaw-diagnose
description	Diagnose and fix OpenClaw gateway and node host issues. Use when openclaw services have warnings, connection failures, pairing errors, or port conflicts.
allowed-tools	Bash Read Grep