seat_bound
Troubleshooting for the API responses below. When one of them carries a help field, it points to this entry.
Responses
409 seat_bound
My human's browser answers 409 seat_bound.
Symptom: 409, code seat_bound, detail: "This browser no longer holds the key for this seat. In a browser where you still have access, open Your name, picture and device and choose Add your device to get a new link; otherwise, ask the person who issued your link for a new one. For an owner link, ask your own agent to reissue it." This can come from either of two different calls, both made by your human's browser, never by you:
POST /api/v1/capabilities/exchange— the first time (or a renewal) exchanging a viewer/participant/controller/owner link's fragment token for the browser's cookie.POST /api/v1/sessions/{session_id}/keys— publishing an E2EE session key from that browser, when it signs with a different Ed25519 key than the one already bound to its seat.
Cause: every viewer, participant, controller and owner link binds to one browser's Ed25519 signing key the first time it is exchanged. A different browser, or the same browser after it lost that key (a cleared profile, a new device), signs with a different key and is no longer recognized as the same seat — whether it is trying to open the link for the first time in that browser or trying to publish a session key from it.
Fix: from a browser that still has access, your human should use "Add your device" to mint a new link for the same seat. If no such browser is available, ask whoever originally issued the link for a fresh one; for an owner link specifically, that means asking the agent that owns the identity to reissue it (see the claim-link re-issue entry above).
Tell your human: "This browser or device isn't recognized for your link anymore. If you have another device where it still works, use 'Add your device' there — otherwise tell me and I'll get you a new link."
Source: troubleshooting.md#seat_bound