PR #64511: fix: use lightweight status RPC for doctor Phase A health gate

• Repository: openclaw/openclaw
• Author: EronFan
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/64511

Description (problem / solution / changelog)

Summary

Fixes issue #64400: CLI and trigger false restarts due to hardcoded 3000ms loopback timeouts.

Problem

When heavily loaded with agents, background crons, or slow RPCs at startup, the OpenClaw gateway can take longer than 3 seconds to respond to health checks. The command's Phase A gate was calling the heavyweight RPC (which probes all channels) via , using the same call path as the detailed health check. This caused false timeouts and triggered unsafe restart paths.

Fix

Replace the heavyweight call in (used for Phase A liveness gating in ) with a direct lightweight RPC call. The method returns a simple gateway status summary without channel probing, making it appropriate for fast liveness checks.

Before:

await healthCommand({ json: false, timeoutMs, config: params.cfg }, params.runtime);

After:

await callGateway({ method: "status", timeoutMs, config: params.cfg });

Also removes unused imports (, ).

Testing

The fast-path mocks already mock , so existing tests are unaffected. The handler is registered in and is lighter than (no channel probing).

Changed files

• src/commands/doctor-gateway-health.ts (modified, +2/-4)

PR #54959: docs: add OpenShell deployment guide

• Repository: openclaw/openclaw
• Author: mjamiv
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/54959

Description (problem / solution / changelog)

Summary

Add a comprehensive deployment guide for running OpenClaw inside NVIDIA OpenShell sandboxes.

The guide covers:

• Prerequisites and quick start with the automated setup script
• Manual step-by-step setup — Docker, gateway, sandbox creation, CoreDNS fix, OpenClaw bundling, Slack configuration
• Network policy — policy structure, the Slack REST/WebSocket split, why *.slack.com wildcards break Socket Mode on v0.0.15+, tls: skip for WebSocket raw TCP passthrough
• WebSocket proxy patch — why the ws library doesn't honor HTTPS_PROXY, the Module._load monkey-patch solution, applicability to Discord gateway connections
• Troubleshooting — DNS failures, WebSocket issues, bot ignoring DMs, npm hangs, gateway corruption
• Known limitations — web_fetch/web_search proxy issues, binary identification requirements

Also adds the new page to the Platforms tab in docs.json navigation.

Related issues

This addresses the documentation gap for sandboxed/proxied deployments. Related issues reporting proxy, WebSocket, and DNS failures in sandboxed environments:

• #49948 — web_fetch proxy issues
• #47598 — WebSocket connection failures
• #46306 — web_search proxy errors
• #50655 — DNS resolution failures in sandboxed environments
• #44980 — proxy configuration issues
• #51049 — sandbox networking problems

Changed files

• docs/.i18n/glossary.zh-CN.json (modified, +28/-0)
• docs/docs.json (modified, +2/-1)
• docs/platforms/openshell.md (added, +836/-0)