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>
32 lines
1.1 KiB
Markdown
32 lines
1.1 KiB
Markdown
---
|
||
summary: "Repository scripts: purpose, scope, and safety notes"
|
||
read_when:
|
||
- Running scripts from the repo
|
||
- Adding or changing scripts under ./scripts
|
||
---
|
||
# Scripts
|
||
|
||
The `scripts/` directory contains helper scripts for local workflows and ops tasks.
|
||
Use these when a task is clearly tied to a script; otherwise prefer the CLI.
|
||
|
||
## Conventions
|
||
|
||
- Scripts are **optional** unless referenced in docs or release checklists.
|
||
- Prefer CLI surfaces when they exist (example: auth monitoring uses `clawdbot models status --check`).
|
||
- Assume scripts are host‑specific; read them before running on a new machine.
|
||
|
||
## Git hooks
|
||
|
||
- `scripts/setup-git-hooks.js`: best-effort setup for `core.hooksPath` when inside a git repo.
|
||
- `scripts/format-staged.js`: pre-commit formatter for staged `src/` and `test/` files.
|
||
|
||
## Auth monitoring scripts
|
||
|
||
Auth monitoring scripts are documented here:
|
||
[/automation/auth-monitoring](/automation/auth-monitoring)
|
||
|
||
## When adding scripts
|
||
|
||
- Keep scripts focused and documented.
|
||
- Add a short entry in the relevant doc (or create one if missing).
|