mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
zooqueen
071e3f1082
Automated rebrand of all openclaw references to hanzo bot: - Package: openclaw -> @hanzo/bot - Binary: openclaw -> hanzo-bot - Config: ~/.openclaw -> ~/.hanzo/bot - Docker: ghcr.io/hanzoai/bot - Env vars: OPENCLAW_* -> BOT_* - Bundle IDs: ai.hanzo.bot.* - Product name: Hanzo Bot
1.4 KiB
1.4 KiB
summary, read_when, title
| summary | read_when | title | |
|---|---|---|---|
| How the macOS app reports gateway/Baileys health states |
|
Health Checks (macOS) |
Health Checks on macOS
How to see whether the linked channel is healthy from the menu bar app.
Menu bar
- Status dot now reflects Baileys health:
- Green: linked + socket opened recently.
- Orange: connecting/retrying.
- Red: logged out or probe failed.
- Secondary line reads "linked · auth 12m" or shows the failure reason.
- "Run Health Check" menu item triggers an on-demand probe.
Settings
- General tab gains a Health card showing: linked auth age, session-store path/count, last check time, last error/status code, and buttons for Run Health Check / Reveal Logs.
- Uses a cached snapshot so the UI loads instantly and falls back gracefully when offline.
- Channels tab surfaces channel status + controls for WhatsApp/Telegram (login QR, logout, probe, last disconnect/error).
How the probe works
- App runs
hanzo-bot health --jsonviaShellExecutorevery ~60s and on demand. The probe loads creds and reports status without sending messages. - Cache the last good snapshot and the last error separately to avoid flicker; show the timestamp of each.
When in doubt
- You can still use the CLI flow in Gateway health (
hanzo-bot status,hanzo-bot status --deep,hanzo-bot health --json) and tail/tmp/hanzoai/bot-*.logforweb-heartbeat/web-reconnect.