agentknock pairing finish

agentknock pairing finish activates the pending pairing after you check its verification code and accept it on the phone.

agentknock pairing finish

The command takes no arguments. It uses the pending pairing saved by pairing start; you don’t pass the address or verification code again. See Pair a client for the complete procedure.

Activation

Agentknock asks the phone to confirm the pairing. It marks the local pairing active only after authenticating the phone’s acceptance, then confirms receipt to the phone. On success, it prints a completion message to standard output. The client can then run commands with secrets and use the secret management commands.

A pending pairing is required. The command returns an error if no pairing exists or if the pairing is already active; it doesn’t start or replace a pairing.

Waiting, interruption, and errors

While waiting, the command reports progress and elapsed time to standard error every 30 seconds. See connection retries for shared waiting behavior.

If the request fails or you interrupt it before activation, the pairing remains pending. You can retry pairing finish after resolving the problem. If the phone rejects the pairing or you abandon it, discard the pending state with pairing abort.

An error can also occur while confirming receipt after the pairing has already become active. Activation is retained in that case. Check pairing status before retrying: an active pairing needs no further finish command. Interrupting after activation leaves it active and ends the command successfully.

If another process replaces the pending pairing while this command waits, the command fails and leaves the replacement unchanged.