Claim a device code
Pairing
Claim a device code
Step two, and not only a read. Looking a pending user_code up while signed in CLAIMS it for that account, which is the binding POST /api/auth/device/approve requires. Skip this call and the approval answers 400 invalid_request.
The Relay app calls this to render the approval sheet. client_id and scope come back only to the person the request is now bound to.
GET
Claim a device code
Authorizations
Better Auth user-session bearer used by the Relay app and by a paired bridge; never an Agent Token.

