> ## Documentation Index
> Fetch the complete documentation index at: https://zju-a00451d9-feat-personal-agent-team.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# pairing

# `velaclaw pairing`

Approve or inspect DM pairing requests (for channels that support pairing).

Related:

* Pairing flow: [Pairing](/channels/pairing)

## Commands

```bash theme={null}
velaclaw pairing list telegram
velaclaw pairing list --channel telegram --account work
velaclaw pairing list telegram --json

velaclaw pairing approve <code>
velaclaw pairing approve telegram <code>
velaclaw 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:

* `velaclaw pairing approve <channel> <code>`
* `velaclaw pairing approve --channel <channel> <code>`
* `velaclaw 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

## 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.