How-To Guides

Mon, 01 Jan 0001 00:00:00 +0000

Pair a mobile device

Run ait applink on the host that holds your aitasks workspace.
The Pairing screen shows a QR code and the underlying applink:// URI.
Open the companion app on your phone (separate aitasks_mobile repo) and tap Scan QR.
The companion app decodes the URI and (once the transport lands) opens a TLS WebSocket back to the host using the pinned certificate fingerprint.

Regenerate the token

Press r on the Pairing screen. A new 256-bit token is drawn and the QR re-renders in place. Any previously issued unused QR becomes invalid immediately — but devices that have already paired keep their long-lived bearer and stay connected. Regenerate is safe to use mid-session.

Reference

Mon, 01 Jan 0001 00:00:00 +0000

Keybindings

Key	Action
`r`	Regenerate the pairing token (Pairing screen)
`s`	Show the Status screen (from Pairing)
`p`	Show the Pairing screen (from Status)
`j`	Open the TUI switcher modal
`q`	Quit

Screens

Pairing

Generates a one-time 256-bit token via secrets.token_urlsafe(32).
Detects the LAN IPv4 and builds the URI per aidocs/applink/protocol.md §Pairing flow.
Renders the URI as a QR code using segno, displayed with half-block Unicode for compact terminal output. The raw URI is not shown on screen to avoid leaking the pairing token to bystanders.

Regenerate semantics

r rotates only the unused pairing token. Devices that have already paired carry their long-lived bearer and keep their connection IDs across a regenerate action.

App Linker on aitasks