dot cloud computer remains Offline/Unavailable; computer-control connection repeatedly refused #50172

What issue are you seeing?

The dot cloud computer remains Offline/Unavailable and cannot be operated, while dot chat remains usable in the macOS app. The affected machine is dot's cloud computer, not the user's local Mac.

Direct, read-only computer-control checks continue to fail. The latest check, performed on 2026-10-02 at 04:09:11–04:09:27 UTC, returned:

failed to connect native pipe: Connection refused (os error 111)

The control tool also reported a kernel reset. This is a tool-observed connection failure, not a diagnosis of the underlying cloud infrastructure.

What steps can reproduce the bug?

In the affected session:

1. Open dot's cloud computer while the dot conversation is still usable.
2. Request the normal read-only inventory of available desktop apps and browser surfaces (cua.getState()).
3. Observe that the cloud computer cannot be connected to or controlled.
4. Reset the computer-control session through its normal reset operation, then make a fresh inventory request. The observed failure persists.

These are reproduction steps for the affected session; reproduction in a separate account or a newly provisioned cloud computer has not been established.

What is the expected behavior?

The cloud computer should become available and allow its desktop and browser surfaces to be enumerated and operated. If it cannot connect, the app should provide a clear recovery path.

Additional information

Environment

• Client: macOS app; exact app build and macOS version have not been captured
• Subscription: ChatGPT Pro
• Affected capability: dot's cloud desktop/computer-control connection
• Observation window: repeated checks from 2026-10-01 20:06 UTC through 2026-10-02 04:09 UTC

Observed sequence

• 2026-10-01 20:06 UTC: The inventory returned no desktop apps and an empty tab list for the cloud Chrome/CDP browser. It reported the native-pipe connection error above and this browser error:

  Protocol error (Target.setDiscoverTargets): Target closed
  

• 2026-10-01 21:43 UTC: A normal control-session reset followed by a fresh inventory request did not restore access.
• Further bounded checks continued to show the availability problem.
• 2026-10-02 04:09 UTC: The latest fresh inventory request again failed with the native-pipe connection error and a reported kernel reset. The earlier browser error was not independently reconfirmed in this latest check.

Impact
Cloud-desktop work involving Inkscape drawing/recording and a YouTube upload remains blocked. Previously retained artifacts are still accessible through separate filesystem/Library access; this report does not establish data loss.

Please investigate the persistent failure to connect to the cloud computer and the available recovery path. No root cause or wider service outage has been established by these observations.