Cloud browser handoff freezes, tab switching fails, and session cannot be truly reset
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
The ChatGPT Work/Codex cloud-browser handoff became unusable during a simple authenticated website workflow. The model could open and inspect pages, but the user-facing browser panel froze, tab switching failed, and attempts to recover created fresh tabs inside the same malfunctioning browser rather than a genuinely reset session.
Observed behavior
- Opened two sites in the cloud browser.
- User could initially see the browser panel but could not switch between tabs.
- Closing one tab and leaving the other did not restore control.
- The side panel then froze.
- Creating a fresh tab and reopening the site still reused the affected browser instance.
- Only one browser instance was exposed, so there was no true session reset or replacement.
- Login/session handoff that had reportedly worked for the same user two days earlier was no longer usable.
- The agent had no integrated mechanism to submit a diagnostic report automatically after repeated browser failures.
Expected behavior
- Reliable tab selection in the user-visible browser panel.
- A true "reset browser session" action that replaces the underlying browser instance.
- Preserved handoff/login continuity where supported.
- Automatic detection of repeated tool/handoff failures.
- A privacy-scrubbed, one-click diagnostic submission flow that returns a tracking/session ID.
Impact
Two explicitly authorized customer-service workflows could not be completed. The model correctly analyzed the tasks, but browser authentication/handoff failures reduced the workflow to manual instructions and caused substantial user frustration.
Privacy
No account credentials, personal financial details, transaction amounts, names, or private session content are included in this report.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified in the report. Start by tracing the cloud-browser handoff, user-facing tab controls, and browser-session lifecycle; done would require reproducible recovery, reliable tab switching, a true session replacement, and the requested diagnostic flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, cloud, frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100