macOS: Opening any local project consistently crashes the desktop app (EXC_BREAKPOINT / SIGTRAP)

Start by inspecting the attached crash logs for builds 5628 and 5551, focusing on the CrBrowserMain stack and the node::fs::FSReqCallback::Resolve path. Trace the local-project opening flow from the point where conversation history becomes visible. Done means opening any local project repeatedly without an EXC_BREAKPOINT crash and keeping the project usable.

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

26.715.61943 (5628)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

The ChatGPT desktop application crashes every time I open any local project.

The issue is 100% reproducible.

The project opens briefly, conversation history becomes visible, and then the application crashes before I can type anything.

The issue affects every local project I have tested.

The problem persists in both build 5551 and build 5628.

What steps can reproduce the bug?

1. Launch the ChatGPT desktop app.

2. Open any existing local project.

3. Wait a few seconds.

The project opens briefly, conversation history appears, and then the application crashes before any interaction is possible.

This happens every time.

crashlog_26.715.61943_build5628_macOS26.5.2.txt

crashlog_26.715.31925_build5551_macOS26.5.2.txt

What is the expected behavior?

Opening a local project should not crash the application.

The project should remain open and fully usable.

Additional information

Environment

• MacBook Air M4
• macOS 26.5.2 (25F84)
• ChatGPT Desktop
• Bundle identifier: com.openai.codex

Affected versions

• 26.715.31925 (build 5551)
• 26.715.61943 (build 5628)

The crash occurs approximately 20 seconds after launching the application, but only after opening a local project.

Troubleshooting already performed

• reinstalled the application
• removed Application Support data
• removed application caches
• reset local application state

The problem persists.

Crash signature

• EXC_BREAKPOINT (SIGTRAP)
• Thread: CrBrowserMain

The stack consistently includes:

• node::fs::FSReqCallback::Resolve
• node::fs::AfterInteger

before returning through V8.

This appears to affect all local projects rather than one corrupted project.

Possibly related to #32676 because the native crash signature is similar, but the reproduction trigger is different: in my case, it occurs consistently when opening any local project, immediately after its conversation history becomes visible.