92697edb7c
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>
1.3 KiB
1.3 KiB
| summary | read_when | ||
|---|---|---|---|
| VPS hosting hub for Clawdbot (Railway/Fly/Hetzner/exe.dev) |
|
VPS hosting
This hub links to the supported VPS/hosting guides and explains how cloud deployments work at a high level.
Pick a provider
- Railway (one‑click + browser setup): Railway
- Fly.io: Fly.io
- Hetzner (Docker): Hetzner
- exe.dev (VM + HTTPS proxy): exe.dev
- AWS (EC2/Lightsail/free tier): works well too. Video guide: https://x.com/techfrenAJ/status/2014934471095812547
How cloud setups work
- The Gateway runs on the VPS and owns state + workspace.
- You connect from your laptop/phone via the Control UI or Tailscale/SSH.
- Treat the VPS as the source of truth and back up the state + workspace.
Remote access: Gateway remote
Platforms hub: Platforms
Using nodes with a VPS
You can keep the Gateway in the cloud and pair nodes on your local devices
(Mac/iOS/Android/headless). Nodes provide local screen/camera/canvas and system.run
capabilities while the Gateway stays in the cloud.