Pairing request
Pairing requests appear in Clients, separately from requests to use secrets. A request connects one command-line client to this phone after you compare its verification code and the client finishes pairing.
Request states
Section titled “Request states”| State | Meaning and available action |
|---|---|
| Waiting | The initial secure exchange hasn’t finished. Wait for the client, or select Reject pairing to abandon the attempt. |
| Compare verification code | The phone has enough information to verify the pairing. Select the code shown by the client, or None of the above. |
| Waiting for client | You accepted the code. Run agentknock pairing finish on the client, or select Reject pairing to withdraw acceptance. |
| Pairing could not continue | The exchange ended or its message couldn’t be verified. The page shows the error. Reject the attempt before starting another. |
| Completed | The phone accepted the client’s finish request and created the pairing. |
| Rejected | No pairing was established from this attempt. |
Only one unfinished pairing is admitted at a time. Waiting, failed, and accepted-but-unfinished attempts all occupy that place until they complete or you reject them. Leaving the page doesn’t reject a request.
Verify and accept
Section titled “Verify and accept”The phone presents three possible verification codes, each containing 12 digits in three groups of four. Compare all digits with the code printed by agentknock pairing start on the computer you intend to pair.
Selecting the matching code accepts it immediately; there is no separate acceptance button. Depending on your device authentication setting, Android may ask you to authenticate first. Canceling or failing authentication leaves the request awaiting a decision.
Selecting a wrong code or None of the above rejects the attempt. It doesn’t offer another guess within the same attempt. Reject a request you didn’t initiate, and don’t accept a different code just to proceed. The pairing guide explains how to investigate a mismatch.
The code verifies that the phone and intended client established the same pairing. The client’s name and reported computer details help you recognize the request, but they don’t replace the code comparison.
Unreadable client details
Section titled “Unreadable client details”Some client details could not be read means the phone verified the secure exchange but couldn’t read the client’s accompanying metadata. The verification code is still usable. Accept only if it matches the intended client’s code; missing host or software information doesn’t by itself make the code invalid.
This differs from Pairing could not continue, where no verifiable code is available and the attempt must be rejected and restarted.
Finish or reject
Section titled “Finish or reject”After you confirm the code, the page displays a copyable agentknock pairing finish command. Run it on the same client. No secrets can be requested through the pending pairing before this step completes.
When the phone processes the finish request, the attempt leaves the pending list and its client details open. If the CLI reports an error during the final exchange, check pairing status there; the phone completing its side doesn’t guarantee that the client received every final message. See pairing finish for retry behavior.
Before completion, Reject pairing remains available while waiting for the exchange or the client. During code comparison, None of the above performs rejection. Rejection takes effect on the phone and removes the attempt from the pending list; the app also tells the relay to revoke it.
If the client still has a pending pairing, clear it with agentknock pairing abort before starting again. Aborting on the client doesn’t reject the phone’s copy, so reject it on the phone as well. A completed pairing is instead ended by revoking the client.
Request information
Section titled “Request information”The page shows the client name, available hostname and platform, and the request time. Technical details adds the pairing address used for this attempt; acceptance and completion times when available; OS version, architecture, and software information; and the client, request, and reported machine IDs.
The pairing address is the address used when this attempt began, even if you later change the phone’s address. Completed and rejected attempts are removed from Clients; their events remain in the audit log for its 365-day retention period.