[macOS] ChatGPT Work cloud-browser manual handoff succeeds but no browser UI appears

Summary

In ChatGPT Work on the macOS desktop app, a manual takeover request for the Cloud Browser reports success, but no browser window, panel, handoff control, screenshot, or other visible UI appears. The user cannot inspect or take over the cloud browser.

Environment

• ChatGPT desktop app: 26.908.40834
• Platform: macOS
• Surface: ChatGPT Work, Cloud Browser
• Observed: 2026-09-12

Steps to reproduce

1. Open a ChatGPT Work conversation in the macOS desktop app.
2. Start a Cloud Browser session and navigate to a safe page such as example.com.
3. Request manual browser takeover.
4. Observe the result after the assistant turn ends.

Expected

The app should surface the active Cloud Browser and a clear takeover control (or show an actionable error if handoff cannot be completed).

Actual

The manual-handoff request returns success, and the assistant turn ends, but nothing appears in the desktop UI. The user sees no browser view, takeover control, screenshot, or popup.

A separate secure sign-in prompt did appear during a sign-in-flow test in the same setup, then was cancelled without entering or submitting credentials. This suggests the missing takeover UI is not simply that all browser prompts/popups are blocked, though the underlying cause is unknown.

Impact

Users cannot watch or manually take over the cloud browser, even when the handoff request reports success. This makes browser work difficult to verify and blocks workflows where user interaction is needed.

Related

This may be related to, but is not the same reproduction as, #37539 (Cloud Browser panel does not surface in ChatGPT Work on the web). This report is specifically for the macOS desktop app and the manual-takeover action.

No private chat content, site credentials, or unrelated personal details are included.

Start by reproducing the manual takeover flow in the macOS desktop app using a ChatGPT Work conversation and a Cloud Browser session on example.com. Trace the handoff result through the desktop UI and compare it with the visible secure sign-in prompt behavior; done means the active browser and takeover control appear, or an actionable error is shown.