openclaw/docs/platforms/index.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.7 KiB

summary read_when
Platform support overview (Gateway + companion apps)
Looking for OS support or install paths
Deciding where to run the Gateway

Platforms

Clawdbot core is written in TypeScript. Node is the recommended runtime. Bun is not recommended for the Gateway (WhatsApp/Telegram bugs).

Companion apps exist for macOS (menu bar app) and mobile nodes (iOS/Android). Windows and Linux companion apps are planned, but the Gateway is fully supported today. Native companion apps for Windows are also planned; the Gateway is recommended via WSL2.

Choose your OS

VPS & hosting

Gateway service install (CLI)

Use one of these (all supported):

  • Wizard (recommended): clawdbot onboard --install-daemon
  • Direct: clawdbot gateway install
  • Configure flow: clawdbot configure → select Gateway service
  • Repair/migrate: clawdbot doctor (offers to install or fix the service)

The service target depends on OS:

  • macOS: LaunchAgent (com.clawdbot.gateway or com.clawdbot.<profile>)
  • Linux/WSL2: systemd user service (clawdbot-gateway[-<profile>].service)