Pairing and reconnecting a phone

Approve the right device and check its current connection state.

Applies to Bridge rc.32

Pair the intended devices

Use Connections on the desktop and the supported phone pairing flow. Confirm the intended account, desktop and phone, then approve the pairing and fingerprint as prompted. Keep QR invitations, device keys and recovery material private.

Pairing is approval

An approved pairing can grant the phone its supported remote-turn capabilities. Workspace and tool permissions still apply. Signing into an account or seeing a saved device row is not proof of a live authorized session.

Reconnect without replaying a change

If a connection drops, refresh the current secure state and keep drafts and attachments intact. When more than one valid host is available, select the intended desktop. The rc.32 reconnect path can reconcile supported project-change results; do not blindly repeat an uncertain mutation.

Revoke a lost device

Use the paired-device controls to revoke the exact lost device and verify the resulting state. A revoked phone must pair again for access. The desktop and selected model endpoint remain responsible for the work.