[ChatGPT Work web] Cloud Browser tab is created but UI never surfaces; CDP refresh times out
Summary
ChatGPT Work on the web can initialize the Cloud Browser backend and return a new tab ID, but the Cloud Browser panel never appears in the chat. Subsequent tab refresh and visibility checks time out, leaving the paid browser feature unusable.
This appears to be a failure between browser provisioning and the user-visible Cloud Browser handoff, not a target-site problem.
Environment
- Subscription: ChatGPT Pro
- Surface: ChatGPT Work on the web
- OS: Windows 10
- Browser: Microsoft Edge 151
- Date observed: August 7, 2026, approximately 10:00 PM Pacific
Reproduction
- Start a ChatGPT Work conversation on the web.
- Ask it to open a cloud browser window.
- The browser runtime reports that Chrome/CDP was selected.
- A fresh browser tab is created and returns tab ID
35. - No Cloud Browser panel, screenshots, replay, or browser window appears in the chat.
- Attempts to inspect or refresh the surfaced browser state time out.
Observed errors
Initial tab discovery:
CDP operation refresh tabs timed out after 20000ms
A direct fresh-tab creation then succeeds:
{ tabId: '35' }
Follow-up visibility checks again fail with:
CDP operation refresh tabs timed out after 20000ms
The user confirms that no Cloud Browser UI appears at any point.
Expected behavior
After a cloud browser is provisioned, the Cloud Browser panel should appear in the chat so the user can inspect the page, screenshots, and replay while the agent operates it.
Actual behavior
The backend reports successful tab creation, but the browser never surfaces in the user interface and cannot be used. A backend tab ID is therefore being treated as success even though the user-visible browser handoff failed.
Impact
This blocks browser-dependent workflows in a paid ChatGPT Pro session. The user reports that Cloud Browser had worked previously and that browser handoff failures have recently occurred across multiple work threads.
Requested investigation
Please check Cloud Browser provisioning, CDP tab refresh, and the web client's browser-panel handoff. The system should also avoid reporting success unless the user-visible Cloud Browser surface is confirmed available.
2 Comments
Escalation: fresh reproduction after initial report
The failure reproduced again on a clean retry shortly after this issue was opened.
Retry 1
A fresh Cloud Browser tab was requested and navigation was attempted to a simple public page with no authentication. The operation failed before the page loaded:
Documented recovery attempt
The existing browser binding was retained, a new fresh tab was requested, and the direct tab/DOM path was used instead of Playwright. That attempt failed with:
No target-site content was reached, no authentication or CAPTCHA was involved, and no Cloud Browser panel appeared in the ChatGPT Work interface.
This is persistent across repeated attempts and multiple work threads, and it is blocking time-sensitive browser-dependent work in a paid ChatGPT Pro session.
Please escalate this for maintainer or on-call triage and correlate the browser provisioning, CDP recovery, and web-client handoff paths. The user-visible browser surface should be part of the success condition; creating a backend tab alone is not a successful browser launch.
I am reproducing the same Cloud Browser failure in a separate user account.
Environment
Current behavior
Cloud Browser initialization starts and a Chrome/CDP browser ID is assigned, but tab discovery fails before any target website can be opened:
Direct creation of a fresh tab also remains unresponsive for more than 30 seconds and times out. This occurs before navigation to WordPress or any other website, so it is not target-site-specific.
Troubleshooting already completed
The problem still reproduces. Another user can use Cloud Browser normally, suggesting this may be isolated to the Cloud Browser session/container or rollout assignment for this account.
Impact
All browser-dependent WordPress administration and website monetization work is blocked.
Request
Please investigate the account-specific Cloud Browser provisioning/session state and, if applicable, forcibly recreate or reset the affected Cloud Browser session/container.