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.5 KiB
1.5 KiB
| summary | read_when | ||
|---|---|---|---|
| CLI reference for `clawdbot plugins` (list, install, enable/disable, doctor) |
|
clawdbot plugins
Manage Gateway plugins/extensions (loaded in-process).
Related:
- Plugin system: Plugins
- Plugin manifest + schema: Plugin manifest
- Security hardening: Security
Commands
clawdbot plugins list
clawdbot plugins info <id>
clawdbot plugins enable <id>
clawdbot plugins disable <id>
clawdbot plugins doctor
clawdbot plugins update <id>
clawdbot plugins update --all
Bundled plugins ship with Clawdbot but start disabled. Use plugins enable to
activate them.
All plugins must ship a clawdbot.plugin.json file with an inline JSON Schema
(configSchema, even if empty). Missing/invalid manifests or schemas prevent
the plugin from loading and fail config validation.
Install
clawdbot plugins install <path-or-spec>
Security note: treat plugin installs like running code. Prefer pinned versions.
Supported archives: .zip, .tgz, .tar.gz, .tar.
Use --link to avoid copying a local directory (adds to plugins.load.paths):
clawdbot plugins install -l ./my-plugin
Update
clawdbot plugins update <id>
clawdbot plugins update --all
clawdbot plugins update <id> --dry-run
Updates only apply to plugins installed from npm (tracked in plugins.installs).