mirror of
https://github.com/openclaw/openclaw.git
synced 2026-05-07 05:00:44 +00:00
6ce1058296
* feat: wire codex diagnostics feedback * fix: harden codex diagnostics hints * fix: neutralize codex diagnostics output * fix: tighten codex diagnostics safeguards * fix: bound codex diagnostics feedback output * fix: tighten codex diagnostics throttling * fix: confirm codex diagnostics uploads * docs: clarify codex diagnostics add-on * fix: route diagnostics through core command * fix: tighten diagnostics authorization * fix: pin diagnostics to bundled codex command * fix: limit owner status in plugin commands * fix: scope diagnostics confirmations * fix: scope codex diagnostics cooldowns * fix: harden codex diagnostics ownership scopes * fix: harden diagnostics command trust and display * fix: keep diagnostics command trust internal * fix: clarify diagnostics exec boundary * fix: consume codex diagnostics confirmations atomically * test: include codex diagnostics binding metadata * test: use string codex binding timestamps * fix: keep reserved command trust host-only * fix: harden diagnostics trust and resume hints * wire diagnostics through exec approval * fix: keep diagnostics tests aligned with bundled root trust * fix telegram diagnostics owner auth * route trajectory exports through exec approval * fix trajectory exec command encoding * fix telegram group owner auth * fix export trajectory approval hardening * fix pairing command owner bootstrap * fix telegram owner exec approvals * fix: make diagnostics approval flow pasteable * fix: route native sensitive command followups * fix: invoke diagnostics exports with current cli * fix: refresh exec approval protocol models * fix: list codex diagnostics from thread bindings * fix: fold codex diagnostics into exec approval * fix: preserve diagnostics approval line breaks * docs: clarify diagnostics codex workflow
78 lines
2.7 KiB
Markdown
78 lines
2.7 KiB
Markdown
---
|
||
summary: "CLI reference for `openclaw pairing` (approve/list pairing requests)"
|
||
read_when:
|
||
- You’re using pairing-mode DMs and need to approve senders
|
||
title: "Pairing"
|
||
---
|
||
|
||
# `openclaw pairing`
|
||
|
||
Approve or inspect DM pairing requests (for channels that support pairing).
|
||
|
||
Related:
|
||
|
||
- Pairing flow: [Pairing](/channels/pairing)
|
||
|
||
## Commands
|
||
|
||
```bash
|
||
openclaw pairing list telegram
|
||
openclaw pairing list --channel telegram --account work
|
||
openclaw pairing list telegram --json
|
||
|
||
openclaw pairing approve <code>
|
||
openclaw pairing approve telegram <code>
|
||
openclaw pairing approve --channel telegram --account work <code> --notify
|
||
```
|
||
|
||
## `pairing list`
|
||
|
||
List pending pairing requests for one channel.
|
||
|
||
Options:
|
||
|
||
- `[channel]`: positional channel id
|
||
- `--channel <channel>`: explicit channel id
|
||
- `--account <accountId>`: account id for multi-account channels
|
||
- `--json`: machine-readable output
|
||
|
||
Notes:
|
||
|
||
- If multiple pairing-capable channels are configured, you must provide a channel either positionally or with `--channel`.
|
||
- Extension channels are allowed as long as the channel id is valid.
|
||
|
||
## `pairing approve`
|
||
|
||
Approve a pending pairing code and allow that sender.
|
||
|
||
Usage:
|
||
|
||
- `openclaw pairing approve <channel> <code>`
|
||
- `openclaw pairing approve --channel <channel> <code>`
|
||
- `openclaw pairing approve <code>` when exactly one pairing-capable channel is configured
|
||
|
||
Options:
|
||
|
||
- `--channel <channel>`: explicit channel id
|
||
- `--account <accountId>`: account id for multi-account channels
|
||
- `--notify`: send a confirmation back to the requester on the same channel
|
||
|
||
Owner bootstrap:
|
||
|
||
- If `commands.ownerAllowFrom` is empty when you approve a pairing code, OpenClaw also records the approved sender as the command owner, using a channel-scoped entry such as `telegram:123456789`.
|
||
- This only bootstraps the first owner. Later pairing approvals do not replace or expand `commands.ownerAllowFrom`.
|
||
- The command owner is the human operator account allowed to run owner-only commands and approve dangerous actions such as `/diagnostics`, `/export-trajectory`, `/config`, and exec approvals.
|
||
|
||
## Notes
|
||
|
||
- Channel input: pass it positionally (`pairing list telegram`) or with `--channel <channel>`.
|
||
- `pairing list` supports `--account <accountId>` for multi-account channels.
|
||
- `pairing approve` supports `--account <accountId>` and `--notify`.
|
||
- If only one pairing-capable channel is configured, `pairing approve <code>` is allowed.
|
||
- If you approved a sender before this bootstrap existed, run `openclaw doctor`; it warns when no command owner is configured and shows the `openclaw config set commands.ownerAllowFrom ...` command to fix it.
|
||
|
||
## Related
|
||
|
||
- [CLI reference](/cli)
|
||
- [Channel pairing](/channels/pairing)
|