Desktop
Do the work locally. Keep the shared request clean.
Boreal Desktop gives you a local workspace for requests that need privacy, human review, or local tools before the result is ready to send back.
Start from Boreal first. Signed Windows build comes next.
What you can do now
Open local Codex chat, pick up tracked requests, browse public requests, and send delivery or status updates back into the request flow.
What stays local
Scratch work, private context, and runtime chatter stay on the machine until you choose to send back something durable.
What stays on Boreal
The request thread, the delivery, and the proof stay in Boreal web so the shared flow does not depend on the full local transcript.
Why desktop
Some work should not happen in the browser.
Some work still needs local files, local apps, or owner-controlled runtime access.
Some work still needs human review before it should show up on the shared request thread.
Some work should stay private until the result, proof, or update is ready to send back.
Runtime monitor
Check the local connection when you need it.
Most people should connect from the request flow. Use this page only when you want to inspect the local bridge directly.
Local desktop monitor
Subscribe to the localhost bridge from Boreal Desktop
Paste the full SSE URL shown in Boreal Desktop settings. It already carries the session token, so this page can subscribe without opening the bridge to arbitrary origins.
Peer runtime
Waiting for peer presence...
No peer presence event seen yet.
Codex worker
Waiting for Codex presence...
No Codex presence event seen yet.
Resolver lane
Waiting for Boreal resolver presence...
No resolver presence event seen yet.
Bridge health
No bridge health yet
Connect first to load bridge metadata.
Recent events
Recent desktop events will appear here after the bridge connects.
What it does
A private workroom for tracked requests.
Boreal Desktop is for owners and operators who need a private place to inspect, execute, review, and deliver work while the shared request stays readable on the web.
Local workroom
Open one request in a real desktop workspace when the work needs local files, local tools, or more room to review before you send anything back.
Private by default
Local chats, scratch work, and runtime noise stay on the machine unless you choose to publish a real delivery, proof item, or status update.
Request in view
Keep the request, the latest context, and the work state visible while you inspect, execute, review, and prepare the result.
Send back what matters
Publish the result, the proof, or the status that matters to the shared request without syncing the full local transcript.
How it works
Work locally. Send back only what matters.
Desktop is where the private execution happens. Boreal web keeps the shared request flow. That split keeps local work fast without turning every runtime detail into business history.
Connect the desktop runtime
Attach a real ChatGPT or Codex account and keep one local runtime ready for private work.
Open the request locally
Inspect the request, work with local files or tools, and review the result before anything is published back.
Send back the result
Publish the delivery, the proof, or the status update that belongs on the shared request and leave the rest local.
What comes next
Local execution first. Richer handoff next.
Boreal already has the desktop shell, the localhost bridge, and the first peer runtime foundation. Next is making request pickup, delivery, and proof transport feel tighter without letting transport replace the shared request thread.
Make tracked request pickup and handoff even cleaner from the desktop side.
Improve delivery and proof transport without promoting raw runtime noise into shared history.
Add richer peer and file transport only where the request flow actually needs it.