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>
62 lines
1.9 KiB
Markdown
62 lines
1.9 KiB
Markdown
---
|
|
summary: "Global voice wake words (Gateway-owned) and how they sync across nodes"
|
|
read_when:
|
|
- Changing voice wake words behavior or defaults
|
|
- Adding new node platforms that need wake word sync
|
|
---
|
|
# Voice Wake (Global Wake Words)
|
|
|
|
Clawdbot treats **wake words as a single global list** owned by the **Gateway**.
|
|
|
|
- There are **no per-node custom wake words**.
|
|
- **Any node/app UI may edit** the list; changes are persisted by the Gateway and broadcast to everyone.
|
|
- Each device still keeps its own **Voice Wake enabled/disabled** toggle (local UX + permissions differ).
|
|
|
|
## Storage (Gateway host)
|
|
|
|
Wake words are stored on the gateway machine at:
|
|
|
|
- `~/.clawdbot/settings/voicewake.json`
|
|
|
|
Shape:
|
|
|
|
```json
|
|
{ "triggers": ["clawd", "claude", "computer"], "updatedAtMs": 1730000000000 }
|
|
```
|
|
|
|
## Protocol
|
|
|
|
### Methods
|
|
|
|
- `voicewake.get` → `{ triggers: string[] }`
|
|
- `voicewake.set` with params `{ triggers: string[] }` → `{ triggers: string[] }`
|
|
|
|
Notes:
|
|
- Triggers are normalized (trimmed, empties dropped). Empty lists fall back to defaults.
|
|
- Limits are enforced for safety (count/length caps).
|
|
|
|
### Events
|
|
|
|
- `voicewake.changed` payload `{ triggers: string[] }`
|
|
|
|
Who receives it:
|
|
- All WebSocket clients (macOS app, WebChat, etc.)
|
|
- All connected nodes (iOS/Android), and also on node connect as an initial “current state” push.
|
|
|
|
## Client behavior
|
|
|
|
### macOS app
|
|
|
|
- Uses the global list to gate `VoiceWakeRuntime` triggers.
|
|
- Editing “Trigger words” in Voice Wake settings calls `voicewake.set` and then relies on the broadcast to keep other clients in sync.
|
|
|
|
### iOS node
|
|
|
|
- Uses the global list for `VoiceWakeManager` trigger detection.
|
|
- Editing Wake Words in Settings calls `voicewake.set` (over the Gateway WS) and also keeps local wake-word detection responsive.
|
|
|
|
### Android node
|
|
|
|
- Exposes a Wake Words editor in Settings.
|
|
- Calls `voicewake.set` over the Gateway WS so edits sync everywhere.
|