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>
39 lines
1.2 KiB
Markdown
39 lines
1.2 KiB
Markdown
---
|
|
summary: "CLI reference for `clawdbot doctor` (health checks + guided repairs)"
|
|
read_when:
|
|
- You have connectivity/auth issues and want guided fixes
|
|
- You updated and want a sanity check
|
|
---
|
|
|
|
# `clawdbot doctor`
|
|
|
|
Health checks + quick fixes for the gateway and channels.
|
|
|
|
Related:
|
|
- Troubleshooting: [Troubleshooting](/gateway/troubleshooting)
|
|
- Security audit: [Security](/gateway/security)
|
|
|
|
## Examples
|
|
|
|
```bash
|
|
clawdbot doctor
|
|
clawdbot doctor --repair
|
|
clawdbot doctor --deep
|
|
```
|
|
|
|
Notes:
|
|
- Interactive prompts (like keychain/OAuth fixes) only run when stdin is a TTY and `--non-interactive` is **not** set. Headless runs (cron, Telegram, no terminal) will skip prompts.
|
|
- `--fix` (alias for `--repair`) writes a backup to `~/.clawdbot/clawdbot.json.bak` and drops unknown config keys, listing each removal.
|
|
|
|
## macOS: `launchctl` env overrides
|
|
|
|
If you previously ran `launchctl setenv CLAWDBOT_GATEWAY_TOKEN ...` (or `...PASSWORD`), that value overrides your config file and can cause persistent “unauthorized” errors.
|
|
|
|
```bash
|
|
launchctl getenv CLAWDBOT_GATEWAY_TOKEN
|
|
launchctl getenv CLAWDBOT_GATEWAY_PASSWORD
|
|
|
|
launchctl unsetenv CLAWDBOT_GATEWAY_TOKEN
|
|
launchctl unsetenv CLAWDBOT_GATEWAY_PASSWORD
|
|
```
|