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.1 KiB

Raw Blame History

summary

read_when

macOS Skills settings UI and gateway-backed status

Updating the macOS Skills settings UI

Changing skills gating or install behavior

Skills (macOS)

The macOS app surfaces Clawdbot skills via the gateway; it does not parse skills locally.

Data source

skills.status (gateway) returns all skills plus eligibility and missing requirements (including allowlist blocks for bundled skills).
Requirements are derived from metadata.clawdbot.requires in each SKILL.md.

Install actions

metadata.clawdbot.install defines install options (brew/node/go/uv).
The app calls skills.install to run installers on the gateway host.
The gateway surfaces only one preferred installer when multiple are provided (brew when available, otherwise node manager from skills.install, default npm).

Env/API keys

The app stores keys in ~/.clawdbot/clawdbot.json under skills.entries.<skillKey>.
skills.update patches enabled, apiKey, and env.

Remote mode

Install + config updates happen on the gateway host (not the local Mac).

1.1 KiB Raw Blame History