Codex desktop in-app browser crashes on browser file import; standalone Chrome works, Firefox works, Edge works.

What version of the Codex App are you using (From “About Codex” dialog)?

OpenAI.Codex_26.623.11225.0 Dump metadata also reports Codex/Chromium file version 149.0.7827.197.

What subscription do you have?

Pro 20x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex desktop crashes/exits when a localhost web app running in the Codex in-app browser imports files through browser filesystem/file picker APIs.

This reproduces with at least two different local web apps:

• Realmz Providence
• ev-nova-web

The same import flow does not crash in standalone Google Chrome on the same machine, which points to Codex desktop’s embedded Chromium/in-app browser integration rather than the web app code.

I captured a dump with ProcDump. The useful dump shows:

• Process: Codex.exe
• Package: OpenAI.Codex_26.623.11225.0
• Codex/Chromium file version: 149.0.7827.197
• Exception: C0000005.ACCESS_VIOLATION
• Faulting module: chrome.dll
• Failure bucket: INVALID_POINTER_READ_c0000005_chrome.dll!Unknown
• Attempted read address: 0x38

The crash appears native. There is no web-app JavaScript exception before the app exits.

The repro field below won't take anything but my feedback ID so here are the repro steps:

1. Open Codex desktop.
2. Open the in-app browser to a localhost web app. In my case: http://localhost:5178/.
3. Trigger the app’s scenario/file import flow, which uses browser file/folder import APIs.
4. Select files/folder through the browser import UI.
5. Codex desktop crashes/exits.

Control check:

• Performing the same import flow in standalone Google Chrome does not crash.
• This reproduces with at least two different local web apps: Realmz Providence and ev-nova-web.

Crash evidence:

• Process: Codex.exe
• Package: OpenAI.Codex_26.623.11225.0
• Codex/Chromium file version: 149.0.7827.197
• Exception: C0000005.ACCESS_VIOLATION
• Faulting module: chrome.dll
• Failure bucket: INVALID_POINTER_READ_c0000005_chrome.dll!Unknown
• Attempted read address: 0x38

What steps can reproduce the bug?

Feedback ID: 019f0a28-654c-7812-9afd-498b9f90eb01

What is the expected behavior?

The in-app browser should allow a localhost web app to import user-selected files/folders without crashing Codex desktop.

If the file import API is unsupported or blocked inside Codex’s in-app browser, the browser should report a recoverable error to the web page instead of terminating the desktop app.

I have a ProcDump-generated dump and CDB analysis available. I can share the analysis text immediately. I would prefer to share the full .dmp privately because it may contain memory, local paths, and session data.

Additional information

_No response_