CONTINUE carries a bounded destination descriptor from the same HANDOFF compatibility contract, so the other device knows what workflow you intended to resume.
2XBR CONTINUE / CROSS-DEVICE HANDOFF V1.0Start here.
Start here.
Continue there.
Take one 2XBR HANDOFF object and its chosen next action to another device. The bytes move directly over temporary WebRTC, the receiving browser re-verifies SHA-256 and destination compatibility, and only then can it stage a fresh local one-use handoff into the selected tool.
Continue on another device →01OBJECTHANDOFF02ACTIONCHOOSE NEXT03DEVICEWEBRTC / DTLS04RESUMEONE-USE LOCAL
READYDIRECT P2P FIRST10 MIN MAXONE OBJECT / ONE ACTION
01 / OBJECT
Bring in one HANDOFF object.
Use HANDOFF → CONTINUE for the cleanest workflow, or choose/paste here directly.
02 / NEXT ACTION
Where should the other device continue?
Load an object first. CONTINUE derives only compatible 2XBR destinations from the same HANDOFF contract.
After SHA-256 verification, the receiving browser profiles the exact received object again and accepts the requested tool only when that destination remains compatible.
The receiver creates a fresh same-origin one-use HANDOFF only after you press CONTINUE. The URL carries only the opaque local handoff identifier.
Pairing lasts ten minutes, one receiver may join, and neither side opens another tool automatically. Every transition remains an explicit user action.
HANDOFF + BEAM = CONTINUITY
The workflow moves, not just the bytes.
CLIP solves clipboard moments. TRAY solves a temporary shelf. CONTINUE solves the harder interruption: you already know what you were doing, and you want the other device to pick up at the next compatible 2XBR action without starting over.
PAIR ONE RECEIVERSESSION 10 MIN MAXFILE 64 MB MAXTEXT 1.5 MB MAXINTEGRITY SHA-256SERVER PAYLOAD NONE