romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92697edb7c
openclaw/docs/platforms/mac/health.md
Jon Shapiro 92697edb7c fix(venice): add compat settings to prevent HTTP 400 errors 
Venice's API doesn't support certain OpenAI-compatible parameters that
Clawdbot sends by default:

- `store`: Venice returns HTTP 400 with no body when this is present
- `developer` role: Not supported by Venice's API

This adds VENICE_COMPAT settings (supportsStore: false,
supportsDeveloperRole: false) to all Venice model definitions, both
from the static catalog and dynamically discovered models.

Fixes issues reported in PR #1666 where users experienced silent
failures (HTTP 400, no body) when using Venice models.

Co-authored-by: jonisjongithub <jonisjongithub@users.noreply.github.com>
Co-authored-by: Clawdbot <bot@clawd.bot>
2026-01-26 17:56:01 -08:00

1.4 KiB
Raw Blame History

summary read_when
How the macOS app reports gateway/Baileys health states
Debugging mac app health indicators

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 clawdbot health --json via ShellExecutor every ~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 (clawdbot status, clawdbot status --deep, clawdbot health --json) and tail /tmp/clawdbot/clawdbot-*.log for web-heartbeat / web-reconnect.