Verifiedon 2026.7.1-2
Action boundary
Before you act
- Expected result
- A layered record states whether the issue is local setup, reachable gateway, or a live channel/account condition.
- Failure mode
- A cached health result or generic doctor recommendation is reported as proof that every configured channel is currently healthy.
- Rollback
- Do not apply a doctor fix automatically; save the diagnostic and return to the relevant configuration or service owner.
Two tools, different questions
openclaw doctor is a local diagnostic and guided-fix surface. openclaw health fetches a gateway health snapshot over WebSocket RPC. Use openclaw health --json for machine-readable evidence. Without --verbose, health can return a snapshot cached for up to 60 seconds; --verbose forces live per-channel account probes and expands the report.
Lab: four-layer observation
Record results for openclaw doctor, openclaw gateway status, openclaw health --json, and—only where relevant—openclaw health --verbose. Label each result local configuration, managed service, gateway snapshot, or live account probe. Do not add a channel or alter credentials while collecting this baseline.
Decision rule
Use doctor --fix only after reading the named issue and identifying the change it intends to make. If a health snapshot contains dead-letter counts, it establishes delivery backlog evidence; it does not authorize resubmitting an event. Continue to the channel-specific inspection first.
Source provenanceVerification and sources
Review receipt rr_cli_health_doctor
- Outcome
- approved
- Method
- source-review
- Reviewer
- forge-independent-review
- Reviewed
Evidence
- openclaw-docs-index — openclaw-main-1237c0c-cli-health; snapshot
51cc0e3dd61a…
Limitations
- Primary-source editorial review; no gateway was connected by this review.
Lesson checkpoint
Ready to move on?
Mark this lesson complete when you can apply its outcome without relying on the examples above.