mirror of
https://github.com/openclaw/openclaw.git
synced 2026-07-15 07:26:06 +00:00
f7d7148cf0
Source-grounded rewrite of 529 published docs pages with per-unit information-loss verification: 1,713 factual corrections cited to src/**, generated surfaces regenerated, frontmatter titles preserved for i18n, release notes pages untouched. All docs gates green. Closes #100141
1.5 KiB
1.5 KiB
summary, read_when, title
| summary | read_when | title | |
|---|---|---|---|
| How the macOS app reports gateway/channel health states |
|
Health checks (macOS) |
Health checks on macOS
How to read the linked-channel health state from the menu bar app.
Menu bar
Status dot:
- Green: linked + probe healthy.
- Orange: linked but a channel probe reports degraded/not connected.
- Red: not linked yet.
The secondary line reads "linked · auth 12m" or shows the failure reason. "Run Health Check Now" in the menu triggers an on-demand probe.
Settings
- General tab shows a Health card: status dot, summary line (link state + auth age), and an optional failure detail line, with Retry now and Open logs buttons.
- Channels tab surfaces per-channel status and controls (login QR, logout, probe, last disconnect/error) for WhatsApp and Telegram.
How the probe works
The app calls the Gateway's health RPC over its existing WebSocket
connection (not a CLI shell-out) every ~60s and on demand. The RPC loads
creds and reports status without sending messages. The app caches the last
good snapshot and the last error separately so the UI loads instantly and
does not flicker while offline.
When in doubt
Use the CLI flow in Gateway health (openclaw status,
openclaw status --deep, openclaw health --json) and tail
/tmp/openclaw/openclaw-*.log, filtering for web-heartbeat / web-reconnect.