openclaw-diagnose
Skill3 starsChanged yesterdayMITView on GitHub
Diagnose and fix OpenClaw gateway and node host issues. Use when openclaw services have warnings, connection failures, pairing errors, or port conflicts.
In this repository31 other files it gives its agents.
- affix-domainsSkill
- apple-designSkill
- apwcli-pairSkill
- ask-always-on-agentSkill
- asus-esc8000-firmware-upgradeSkill
- asus-esc8000-gpu-bios-tuningSkill
- build-stealth-rustdeskSkill
- chrome-cdp-setupSkill
- cua-macos-lume-sandboxSkill
- deploy-kimi-k26-on-rtx-pro-6000Skill
- deploy-kimi-k3-on-rtx-pro-6000Skill
- deploy-stealth-rustdeskSkill
- ghostty-terminfoSkill
- herdr-rename-hookSkill
- imsg-permissionsSkill
- llm-inference-benchmarkSkill
- lxd-docker-firewall-conflictSkill
- mac-mini-as-headless-serverSkill
- macos-app-multi-instancesSkill
- macos-smb-serverSkill
- mac-smb-automountSkill
- paseo-profilesSkill
- private-fork-syncSkill
- refresh-claude-accountSkill
- ssh-claude-authSkill
- sync-claude-accountsSkill
- to-featuresSkill
- trusted-publishSkill
- ubuntu-lxd-gpu-serverSkill
- ubuntu-nvidia-gpu-enablementSkill
- ubuntu-zfs-mirror-installSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
When the user asks you to diagnose or fix OpenClaw gateway/node issues, follow this structured investigation.
- Distinctive: line 13
Run these in parallel:
- Distinctive: line 24
Look for these common issues:
- Very specific: line 27
Check if both ai.openclaw.gateway and ai.openclaw.node are registered as LaunchAgents
- Very specific: line 28
Use launchctl print gui/$(id -u)/<label> to inspect each service
- Very specific: line 29
Use lsof -iTCP:<port> -sTCP:LISTEN -P to confirm which process owns the port
- Very specific: line 33
Check ~/.openclaw/logs/node.err.log for pairing required or ECONNREFUSED
- Very specific: line 34
If the node shows "pairing required", run openclaw nodes pending to find the pending request
- Very specific: line 40
Check if gateway is listening: lsof -iTCP:<port> -sTCP:LISTEN -P
- Very specific: line 41
If gateway is down: openclaw gateway restart
- Distinctive: line 46
After taking corrective action, confirm health:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 pendingStep 2: Analyze warnings
Look for these common issues:
Multiple gateway-like services detected
- Check if both
ai.openclaw.gatewayandai.openclaw.nodeare registered as LaunchAgents - Use
launchctl print gui/$(id -u)/<label>to inspect each service - Use
lsof -iTCP:<port> -sTCP:LISTEN -Pto 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.logforpairing requiredorECONNREFUSED - If the node shows "pairing required", run
openclaw nodes pendingto 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: trueso 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 errorsKey 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
--hostand--portflags onopenclaw node runspecify 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.logand~/.openclaw/logs/node.err.log
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

