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>
21 lines
1016 B
Markdown
21 lines
1016 B
Markdown
---
|
|
summary: "Reaction semantics shared across channels"
|
|
read_when:
|
|
- Working on reactions in any channel
|
|
---
|
|
# Reaction tooling
|
|
|
|
Shared reaction semantics across channels:
|
|
|
|
- `emoji` is required when adding a reaction.
|
|
- `emoji=""` removes the bot's reaction(s) when supported.
|
|
- `remove: true` removes the specified emoji when supported (requires `emoji`).
|
|
|
|
Channel notes:
|
|
|
|
- **Discord/Slack**: empty `emoji` removes all of the bot's reactions on the message; `remove: true` removes just that emoji.
|
|
- **Google Chat**: empty `emoji` removes the app's reactions on the message; `remove: true` removes just that emoji.
|
|
- **Telegram**: empty `emoji` removes the bot's reactions; `remove: true` also removes reactions but still requires a non-empty `emoji` for tool validation.
|
|
- **WhatsApp**: empty `emoji` removes the bot reaction; `remove: true` maps to empty emoji (still requires `emoji`).
|
|
- **Signal**: inbound reaction notifications emit system events when `channels.signal.reactionNotifications` is enabled.
|