[Windows][26.825.6671.0] Built-in Browser crashes entire app in both ChatGPT and Codex modes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.825.6671.0 x64
What subscription do you have?
Enterprise
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What issue are you seeing?
What version are you using?
Microsoft Store package: OpenAI.Codex 26.825.6671.0 x64
ChatGPT.exe / Chromium version: 151.0.7922.174
What subscription do you have?
[ENTER PLAN: Free, Plus, Pro, Business, Enterprise, or Edu]
What platform are you using?
Windows 11 24H2, build 26100, x64
CPU: Intel Core i7-1365U
GPU: Intel Iris Xe
GPU driver: 32.0.101.7084
What issue are you seeing?
The complete ChatGPT desktop application immediately exits whenever the
built-in Browser is initialized.
The crash occurs in both product modes:
- When ChatGPT is selected and the Browser sidebar is opened.
- When Codex is selected and the Browser sidebar is opened.
- When ChatGPT or Codex automatically invokes Browser during a workflow
while answering a question.
The crash is therefore not limited to manually opening the sidebar. Browser
Use invoked programmatically during an answer causes the same full-application
termination.
One example occurred during the last workflow step in the task titled:
"Discuss ChatGPT support use cases"
That workflow proceeded normally until Browser was invoked, at which point
the entire desktop app exited.
Expected behavior
The Browser sidebar should open and remain usable. Browser Use during an
answer should complete normally. If the browser process fails, the error
should be contained without terminating the desktop application.
Actual behavior
The complete desktop application exits immediately when Browser initializes,
whether Browser was opened manually or invoked automatically during a workflow.
Crash evidence
A clean-install reproduction occurred at:
2026-08-31 10:27:05 AM America/New_York
Crashpad sidecar:
{"capture_kind":"crash","osarch":"x86_64","ptype":"browser"}
The same Crashpad browser-process signature was recorded repeatedly before
and after Repair, Reset, and reinstall.
Windows also previously recorded:
Event: RADAR_PRE_LEAK_64
Process: ChatGPT.exe
Version: 151.0.7922.174
No corresponding Intel GPU, display-driver, or Windows Code Integrity failure
was found.
Troubleshooting completed
- Cleared built-in Browser cookies, history, and login state
- Restarted the desktop app
- Restarted Windows
- Verified adequate CPU, memory, and free storage
- Disconnected the DisplayLink dock and reproduced using only the internal display
- Ran Windows App Repair
- Ran Windows App Reset
- Completely uninstalled the application
- Restarted Windows
- Reinstalled from the Microsoft Store
- Reproduced immediately after the clean installation
The clean installation generated the same Crashpad signature:
capture_kind=crash
ptype=browser
Additional information
The problem affects both ChatGPT and Codex selections within the combined
Windows desktop application. It affects both manually opened Browser sessions
and Browser Use initiated by an answering workflow.
What steps can reproduce the bug?
Steps to reproduce manually
- Start the ChatGPT Windows desktop application.
- Select ChatGPT or Codex.
- Open the built-in Browser sidebar.
- The entire application immediately exits.
Steps to reproduce through a workflow
- Start a conversation in ChatGPT or Codex.
- Ask a question or start a workflow that requires Browser Use.
- Allow the workflow to proceed until Browser is invoked.
- The entire application immediately exits.
What is the expected behavior?
Browser opens as expected or completes answer if browser workflow is used
Additional information
No response
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
Start by reproducing the crash when the built-in Browser sidebar initializes or when Browser Use is invoked in the Windows desktop app, then inspect the Crashpad browser-process signature. Done means Browser opens and workflow browser use completes without terminating the application, including when the browser process fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100