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>
84 lines
2.5 KiB
Markdown
84 lines
2.5 KiB
Markdown
---
|
||
summary: "Pairing overview: approve who can DM you + which nodes can join"
|
||
read_when:
|
||
- Setting up DM access control
|
||
- Pairing a new iOS/Android node
|
||
- Reviewing Clawdbot security posture
|
||
---
|
||
|
||
# Pairing
|
||
|
||
“Pairing” is Clawdbot’s explicit **owner approval** step.
|
||
It is used in two places:
|
||
|
||
1) **DM pairing** (who is allowed to talk to the bot)
|
||
2) **Node pairing** (which devices/nodes are allowed to join the gateway network)
|
||
|
||
Security context: [Security](/gateway/security)
|
||
|
||
## 1) DM pairing (inbound chat access)
|
||
|
||
When a channel is configured with DM policy `pairing`, unknown senders get a short code and their message is **not processed** until you approve.
|
||
|
||
Default DM policies are documented in: [Security](/gateway/security)
|
||
|
||
Pairing codes:
|
||
- 8 characters, uppercase, no ambiguous chars (`0O1I`).
|
||
- **Expire after 1 hour**. The bot only sends the pairing message when a new request is created (roughly once per hour per sender).
|
||
- Pending DM pairing requests are capped at **3 per channel** by default; additional requests are ignored until one expires or is approved.
|
||
|
||
### Approve a sender
|
||
|
||
```bash
|
||
clawdbot pairing list telegram
|
||
clawdbot pairing approve telegram <CODE>
|
||
```
|
||
|
||
Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `slack`.
|
||
|
||
### Where the state lives
|
||
|
||
Stored under `~/.clawdbot/credentials/`:
|
||
- Pending requests: `<channel>-pairing.json`
|
||
- Approved allowlist store: `<channel>-allowFrom.json`
|
||
|
||
Treat these as sensitive (they gate access to your assistant).
|
||
|
||
|
||
## 2) Node device pairing (iOS/Android/macOS/headless nodes)
|
||
|
||
Nodes connect to the Gateway as **devices** with `role: node`. The Gateway
|
||
creates a device pairing request that must be approved.
|
||
|
||
### Approve a node device
|
||
|
||
```bash
|
||
clawdbot devices list
|
||
clawdbot devices approve <requestId>
|
||
clawdbot devices reject <requestId>
|
||
```
|
||
|
||
### Where the state lives
|
||
|
||
Stored under `~/.clawdbot/devices/`:
|
||
- `pending.json` (short-lived; pending requests expire)
|
||
- `paired.json` (paired devices + tokens)
|
||
|
||
### Notes
|
||
|
||
- The legacy `node.pair.*` API (CLI: `clawdbot nodes pending/approve`) is a
|
||
separate gateway-owned pairing store. WS nodes still require device pairing.
|
||
|
||
|
||
## Related docs
|
||
|
||
- Security model + prompt injection: [Security](/gateway/security)
|
||
- Updating safely (run doctor): [Updating](/install/updating)
|
||
- Channel configs:
|
||
- Telegram: [Telegram](/channels/telegram)
|
||
- WhatsApp: [WhatsApp](/channels/whatsapp)
|
||
- Signal: [Signal](/channels/signal)
|
||
- iMessage: [iMessage](/channels/imessage)
|
||
- Discord: [Discord](/channels/discord)
|
||
- Slack: [Slack](/channels/slack)
|