mirror of https://github.com/hanzoai/bot.git synced 2026-11-01 17:14:58 +00:00

Files

T

zooqueen 071e3f1082 rebrand: openclaw -> hanzo bot across entire codebase

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

2026-03-19 13:52:32 -07:00

3.2 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Health check steps for channel connectivity

Diagnosing WhatsApp channel health

Health Checks

Health Checks (CLI)

Short guide to verify channel connectivity without guessing.

Quick checks

hanzo-bot status — local summary: gateway reachability/mode, update hint, linked channel auth age, sessions + recent activity.
hanzo-bot status --all — full local diagnosis (read-only, color, safe to paste for debugging).
hanzo-bot status --deep — also probes the running Gateway (per-channel probes when supported).
hanzo-bot health --json — asks the running Gateway for a full health snapshot (WS-only; no direct Baileys socket).
Send /status as a standalone message in WhatsApp/WebChat to get a status reply without invoking the agent.
Logs: tail /tmp/hanzoai/bot-*.log and filter for web-heartbeat, web-reconnect, web-auto-reply, web-inbound.

Deep diagnostics

Creds on disk: ls -l ~/.hanzo/bot/credentials/whatsapp/<accountId>/creds.json (mtime should be recent).
Session store: ls -l ~/.hanzo/bot/agents/<agentId>/sessions/sessions.json (path can be overridden in config). Count and recent recipients are surfaced via status.
Relink flow: hanzo-bot channels logout && hanzo-bot channels login --verbose when status codes 409–515 or loggedOut appear in logs. (Note: the QR login flow auto-restarts once for status 515 after pairing.)

Health monitor config

gateway.channelHealthCheckMinutes: how often the gateway checks channel health. Default: 5. Set 0 to disable health-monitor restarts globally.
gateway.channelStaleEventThresholdMinutes: how long a connected channel can stay idle before the health monitor treats it as stale and restarts it. Default: 30. Keep this greater than or equal to gateway.channelHealthCheckMinutes.
gateway.channelMaxRestartsPerHour: rolling one-hour cap for health-monitor restarts per channel/account. Default: 10.
channels.<provider>.healthMonitor.enabled: disable health-monitor restarts for a specific channel while leaving global monitoring enabled.
channels.<provider>.accounts.<accountId>.healthMonitor.enabled: multi-account override that wins over the channel-level setting.
These per-channel overrides apply to the built-in channel monitors that expose them today: Discord, Google Chat, iMessage, Microsoft Teams, Signal, Slack, Telegram, and WhatsApp.

When something fails

logged out or status 409–515 → relink with hanzo-bot channels logout then hanzo-bot channels login.
Gateway unreachable → start it: hanzo-bot gateway --port 18789 (use --force if the port is busy).
No inbound messages → confirm linked phone is online and the sender is allowed (channels.whatsapp.allowFrom); for group chats, ensure allowlist + mention rules match (channels.whatsapp.groups, agents.list[].groupChat.mentionPatterns).

Dedicated "health" command

hanzo-bot health --json asks the running Gateway for its health snapshot (no direct channel sockets from the CLI). It reports linked creds/auth age when available, per-channel probe summaries, session-store summary, and a probe duration. It exits non-zero if the Gateway is unreachable or the probe fails/timeouts. Use --timeout <ms> to override the 10s default.

3.2 KiB Raw Permalink Blame History Unescape Escape