docs/cli/pairing.md
openclaw pairingApprove or inspect DM pairing requests (for channels that support pairing).
Related:
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 listList 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 outputNotes:
--channel.pairing approveApprove 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 configuredOptions:
--channel <channel>: explicit channel id--account <accountId>: account id for multi-account channels--notify: send a confirmation back to the requester on the same channelOwner bootstrap:
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.commands.ownerAllowFrom./diagnostics, /export-trajectory, /config, and exec approvals.pairing list telegram) or with --channel <channel>.pairing list supports --account <accountId> for multi-account channels.pairing approve supports --account <accountId> and --notify.pairing approve <code> is allowed.openclaw doctor; it warns when no command owner is configured and shows the openclaw config set commands.ownerAllowFrom ... command to fix it.