Short guide to verify channel connectivity without guessing.
coderclaw status — local summary: gateway reachability/mode, update hint, linked channel auth age, sessions + recent activity.coderclaw status --all — full local diagnosis (read-only, color, safe to paste for debugging).coderclaw status --deep — also probes the running Gateway (per-channel probes when supported).coderclaw health --json — asks the running Gateway for a full health snapshot (WS-only; no direct Baileys socket)./status as a standalone message in WhatsApp/WebChat to get a status reply without invoking the agent./tmp/coderclaw/coderclaw-*.log and filter for web-heartbeat, web-reconnect, web-auto-reply, web-inbound.ls -l ~/.coderclaw/credentials/whatsapp/<accountId>/creds.json (mtime should be recent).ls -l ~/.coderclaw/agents/<agentId>/sessions/sessions.json (path can be overridden in config). Count and recent recipients are surfaced via status.coderclaw channels logout && coderclaw 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.)logged out or status 409–515 → relink with coderclaw channels logout then coderclaw channels login.coderclaw gateway --port 18789 (use --force if the port is busy).channels.whatsapp.allowFrom); for group chats, ensure allowlist + mention rules match (channels.whatsapp.groups, agents.list[].groupChat.mentionPatterns).coderclaw 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.