Local PC stays Offline in dot

“Despite the host being awake, the desktop app being open, and the current conversation running locally on the PC, dot still reports the PC as Offline.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/14733/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Local Windows PC stays Offline in dot Remote Control. Persists after restarting the PC, restarting the desktop app and signing in again, while the PC is in use.

Is this your bug?

File my report

Where: dot Remote Control
Error text: Failed to resume chat: Codex app-server is not available
Versions: 26.928.21956
Platforms: Windows
How bad: Stops work: a core feature can't be used.

Part of: Cloud WebSocket ignores proxy3 bugs

Dot-created tasks fail to open in desktop behind a proxy6 people
Durable host WebSocket ignores proxy2 people

Not quite your bug?

Stuck on startup splash7 people
Desktop requests expire queued after RPC stalls fill in-flight slots4 people
Dot cannot read local threads57 people

Original reports2, newest first

Sep 30, 2026[Windows][dot] Local PC stays Offline; CLI WebSocket handshake succeeds with explicit HTTP proxyOn GitHub#49626
Sep 30, 2026Windows Remote Control: dot shows active local PC as Offline after restart and re-loginOn GitHub#49539