No active project yet.
Drop an object above. You do not need to create a project for one-off work.
START WITH A FILE →2XBR DESK / PRIMARY WORKBENCHBring it in.
Bring it in.
Get it done.
Start with a file, project or outcome. DESK gives you one place to resume work, run a repeatable job, check integrity, send to another device or package the result. Specialized engines stay underneath unless you deliberately open them.
Open Desk →STARTFILE / INTENT→DOONE CLEAR ACTION→CHECKINTEGRITY / TRUST→SENDWHEN YOU CHOOSE
DESK / LOCAL WORKBENCHNO CLOUD ACCOUNTNO LOOPBACK PROBE ON LOADEXPLICIT ACTIONS ONLY
START / INPUT → GOAL → NEXT STEPGive 2XBR the thing.
Give 2XBR the thing.
Tell it what you want.
DESK is the front door to 2XBR. Add an input, add a goal when you have one, and continue to a bounded next step. If both are present, DESK keeps them together while the real object is still re-checked locally before a plan appears.
01 / INPUT / FILEDROP SOMETHING INFILE · PROOF · CASE · AUDIT · DELTA · ARCHIVE · OTHER
02 / GOAL / OPTIONAL2XBR RECHECKS THE REAL OBJECT BEFORE ANY ACTION
RUN LEDGER…0 entriesTRUSTED SIGNERS…0 blockedSAVED ROUTES…route memoriesGUARDRAILS…0 plans
TRUSTED DEVICES—
BRIDGELOCAL —
No trusted device is stored yet.
RECENT ACTIVITY
RUN HISTORY →What happened in this browser.
No project activity yet.
One-off tools can remain ephemeral. Project executions will appear here when local run evidence exists.
RECENT / FAVORITES
LOCAL ONLYPick up where you left off.
RECENT
No recent platform routes yet.
FAVORITES
Star commands in ⌘K and they will surface here.
DESK reads bounded browser-local state. Files, project names and recent work are not uploaded just to make the workbench function.
Public web checks, device transfer and relay use begin from an intentional action. Opening DESK does not create a hidden network workflow.
Native BRIDGE capabilities remain separately granted and bounded. Consolidation does not widen filesystem, process or network authority.
Integrity-sensitive changes, received artifacts and trusted handoffs keep their existing verification gates and stop when required evidence is missing.
No scheduler or hidden background runner is introduced. Mutation, approval, signing and transfer remain explicit user actions.
Routes, approvals, working objects and evidence keep visible limits and lifecycle controls instead of silently becoming permanent cloud history.
LOCAL STATE / READY