AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Openclaw Diagnose

skill-soulmachine-skills-openclaw-diagnose · by soulmachine

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

↗ Repository
— No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-soulmachine-skills-openclaw-diagnose

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ● Network access Used
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-soulmachine-skills-openclaw-diagnose)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Openclaw Diagnose? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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)/ to inspect each service
  • Use lsof -iTCP: -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
  • 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: -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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills