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

26.513.3673.0

What subscription do you have?

pro

What platform is your computer?

Windows x64

What issue are you seeing?

Codex Desktop bug report: LocalConversationPage crashes when opening some existing chats

Summary

Some existing Codex Desktop conversations cannot be opened anymore. When clicking the affected chats, the UI shows a generic error page:

糟糕，出错了

New or unaffected conversations still work, but multiple historical conversations crash the local conversation page, making the app hard to use.

Environment

• App: OpenAI Codex Desktop, Microsoft Store build
• Codex App version: 26.513.3673.0
• Package: OpenAI.Codex_26.513.3673.0_x64__2p2nqsd0c76g0
• Platform: Windows x64
• Workspace path pattern involved: Windows absolute paths, for example C:\Users\<user>\Desktop\D3-Code\delivery-java\delivery-rebuild-order-service
• Local timezone: Asia/Shanghai

Reproduction Steps

1. Open Codex Desktop on Windows.
2. Open an existing historical conversation that contains previous work in a Windows workspace.
3. The conversation initially routes/resumes successfully.
4. The UI then crashes into the generic error boundary page: 糟糕，出错了.
5. Clicking retry does not reliably recover the affected conversation.

Actual Result

The local conversation page crashes while rendering a previously completed thread.

Expected Result

Codex Desktop should render the conversation history successfully. If one historical item cannot be parsed or rendered, the app should isolate that item and keep the conversation usable instead of crashing the whole page.

Key Local Log Evidence

Log file:

C:\Users\<user>\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Codex\Logs\2026\05\16\codex-desktop-5665250b-2bd7-41b4-ae8b-8bfad293a06d-21412-t0-i1-050704-0.log

Observed around 2026-05-16 13:08 to 13:19 local time.

The thread resume itself succeeds, then the page crashes:

maybe_resume_success conversationId=019dadb2-4957-7dd0-b7d2-908445b3e30b latestTurnStatus=completed markedStreaming=true
error [electron-message-handler] error boundary ... name=LocalConversationPage
errorMessage="invalid syntax at line 1 col 5:

1  cwd=\"C:\\Users\\<user>\\Desktop\\D3-Code\\delivery-java\\delivery-rebuild-order-service\"
       ^"

The stack includes:

markdown-D32gobzN.js
local-conversation-thread-BKrlVhAv.js
review-file-source-tab-BmlwHNat.js
local-conversation-page-Vm2E5OJ5.js
LocalConversationPage

This repeats for multiple affected conversations, including:

019dadb2-4957-7dd0-b7d2-908445b3e30b
019d7002-1387-7ee3-8b15-5e7bebca7ac9
019dfe16-b386-7973-9d9f-d0d72e6740d8

There are also benign-looking thread/goal/get failures:

error={"code":-32600,"message":"goals feature is disabled"}

But the page crash happens after successful thread/resume / maybe_resume_success, and the fatal symptom is the LocalConversationPage error boundary with invalid syntax at line 1 col 5 while parsing a cwd="C:\..." line.

Local Data Integrity Check

The local thread database was checked separately:

• C:\Users\<user>\.codex\state_5.sqlite
• Total thread rollout paths checked: 107
• Missing rollout paths: 0
• Empty rollout paths: 0
• Invalid sampled rollout files: 0

So this does not look like missing local conversation files. It looks like a frontend rendering/parsing crash for specific historical content.

Suspected Cause

The renderer appears to parse a Windows command/source/review snippet containing:

cwd="C:\Users\<user>\Desktop\D3-Code\delivery-java\delivery-rebuild-order-service"

as a syntax item, fails at column 5, and throws through review-file-source-tab / markdown rendering, crashing the full LocalConversationPage.

Impact

This makes multiple existing conversations unusable. The user cannot reliably reopen important historical threads, and normal app usage is blocked because clicking affected conversations crashes the page.

Request

Please fix the Codex Desktop renderer so invalid or unexpected historical source/review/markdown content is isolated instead of crashing the whole conversation page. A fallback rendering path for unparsable source snippets would unblock affected users.

What steps can reproduce the bug?

Codex Desktop bug report: LocalConversationPage crashes when opening some existing chats

Summary

Some existing Codex Desktop conversations cannot be opened anymore. When clicking the affected chats, the UI shows a generic error page:

糟糕，出错了

New or unaffected conversations still work, but multiple historical conversations crash the local conversation page, making the app hard to use.

Environment

• App: OpenAI Codex Desktop, Microsoft Store build
• Codex App version: 26.513.3673.0
• Package: OpenAI.Codex_26.513.3673.0_x64__2p2nqsd0c76g0
• Platform: Windows x64
• Workspace path pattern involved: Windows absolute paths, for example C:\Users\<user>\Desktop\D3-Code\delivery-java\delivery-rebuild-order-service
• Local timezone: Asia/Shanghai

Reproduction Steps

1. Open Codex Desktop on Windows.
2. Open an existing historical conversation that contains previous work in a Windows workspace.
3. The conversation initially routes/resumes successfully.
4. The UI then crashes into the generic error boundary page: 糟糕，出错了.
5. Clicking retry does not reliably recover the affected conversation.

Actual Result

The local conversation page crashes while rendering a previously completed thread.

Expected Result

Codex Desktop should render the conversation history successfully. If one historical item cannot be parsed or rendered, the app should isolate that item and keep the conversation usable instead of crashing the whole page.

Key Local Log Evidence

Log file:

C:\Users\<user>\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Codex\Logs\2026\05\16\codex-desktop-5665250b-2bd7-41b4-ae8b-8bfad293a06d-21412-t0-i1-050704-0.log

Observed around 2026-05-16 13:08 to 13:19 local time.

The thread resume itself succeeds, then the page crashes:

maybe_resume_success conversationId=019dadb2-4957-7dd0-b7d2-908445b3e30b latestTurnStatus=completed markedStreaming=true
error [electron-message-handler] error boundary ... name=LocalConversationPage
errorMessage="invalid syntax at line 1 col 5:

1  cwd=\"C:\\Users\\<user>\\Desktop\\D3-Code\\delivery-java\\delivery-rebuild-order-service\"
       ^"

The stack includes:

markdown-D32gobzN.js
local-conversation-thread-BKrlVhAv.js
review-file-source-tab-BmlwHNat.js
local-conversation-page-Vm2E5OJ5.js
LocalConversationPage

This repeats for multiple affected conversations, including:

019dadb2-4957-7dd0-b7d2-908445b3e30b
019d7002-1387-7ee3-8b15-5e7bebca7ac9
019dfe16-b386-7973-9d9f-d0d72e6740d8

There are also benign-looking thread/goal/get failures:

error={"code":-32600,"message":"goals feature is disabled"}

But the page crash happens after successful thread/resume / maybe_resume_success, and the fatal symptom is the LocalConversationPage error boundary with invalid syntax at line 1 col 5 while parsing a cwd="C:\..." line.

Local Data Integrity Check

The local thread database was checked separately:

• C:\Users\<user>\.codex\state_5.sqlite
• Total thread rollout paths checked: 107
• Missing rollout paths: 0
• Empty rollout paths: 0
• Invalid sampled rollout files: 0

So this does not look like missing local conversation files. It looks like a frontend rendering/parsing crash for specific historical content.

Suspected Cause

The renderer appears to parse a Windows command/source/review snippet containing:

cwd="C:\Users\<user>\Desktop\D3-Code\delivery-java\delivery-rebuild-order-service"

as a syntax item, fails at column 5, and throws through review-file-source-tab / markdown rendering, crashing the full LocalConversationPage.

Impact

This makes multiple existing conversations unusable. The user cannot reliably reopen important historical threads, and normal app usage is blocked because clicking affected conversations crashes the page.

Request

Please fix the Codex Desktop renderer so invalid or unexpected historical source/review/markdown content is isolated instead of crashing the whole conversation page. A fallback rendering path for unparsable source snippets would unblock affected users.

What is the expected behavior?

Codex Desktop bug report: LocalConversationPage crashes when opening some existing chats

Summary

Some existing Codex Desktop conversations cannot be opened anymore. When clicking the affected chats, the UI shows a generic error page:

糟糕，出错了

New or unaffected conversations still work, but multiple historical conversations crash the local conversation page, making the app hard to use.

Environment

• App: OpenAI Codex Desktop, Microsoft Store build
• Codex App version: 26.513.3673.0
• Package: OpenAI.Codex_26.513.3673.0_x64__2p2nqsd0c76g0
• Platform: Windows x64
• Workspace path pattern involved: Windows absolute paths, for example C:\Users\<user>\Desktop\D3-Code\delivery-java\delivery-rebuild-order-service
• Local timezone: Asia/Shanghai

Reproduction Steps

1. Open Codex Desktop on Windows.
2. Open an existing historical conversation that contains previous work in a Windows workspace.
3. The conversation initially routes/resumes successfully.
4. The UI then crashes into the generic error boundary page: 糟糕，出错了.
5. Clicking retry does not reliably recover the affected conversation.

Actual Result

The local conversation page crashes while rendering a previously completed thread.

Expected Result

Codex Desktop should render the conversation history successfully. If one historical item cannot be parsed or rendered, the app should isolate that item and keep the conversation usable instead of crashing the whole page.

Key Local Log Evidence

Log file:

C:\Users\<user>\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Codex\Logs\2026\05\16\codex-desktop-5665250b-2bd7-41b4-ae8b-8bfad293a06d-21412-t0-i1-050704-0.log

Observed around 2026-05-16 13:08 to 13:19 local time.

The thread resume itself succeeds, then the page crashes:

maybe_resume_success conversationId=019dadb2-4957-7dd0-b7d2-908445b3e30b latestTurnStatus=completed markedStreaming=true
error [electron-message-handler] error boundary ... name=LocalConversationPage
errorMessage="invalid syntax at line 1 col 5:

1  cwd=\"C:\\Users\\<user>\\Desktop\\D3-Code\\delivery-java\\delivery-rebuild-order-service\"
       ^"

The stack includes:

markdown-D32gobzN.js
local-conversation-thread-BKrlVhAv.js
review-file-source-tab-BmlwHNat.js
local-conversation-page-Vm2E5OJ5.js
LocalConversationPage

This repeats for multiple affected conversations, including:

019dadb2-4957-7dd0-b7d2-908445b3e30b
019d7002-1387-7ee3-8b15-5e7bebca7ac9
019dfe16-b386-7973-9d9f-d0d72e6740d8

There are also benign-looking thread/goal/get failures:

error={"code":-32600,"message":"goals feature is disabled"}

But the page crash happens after successful thread/resume / maybe_resume_success, and the fatal symptom is the LocalConversationPage error boundary with invalid syntax at line 1 col 5 while parsing a cwd="C:\..." line.

Local Data Integrity Check

The local thread database was checked separately:

• C:\Users\<user>\.codex\state_5.sqlite
• Total thread rollout paths checked: 107
• Missing rollout paths: 0
• Empty rollout paths: 0
• Invalid sampled rollout files: 0

So this does not look like missing local conversation files. It looks like a frontend rendering/parsing crash for specific historical content.

Suspected Cause

The renderer appears to parse a Windows command/source/review snippet containing:

cwd="C:\Users\<user>\Desktop\D3-Code\delivery-java\delivery-rebuild-order-service"

as a syntax item, fails at column 5, and throws through review-file-source-tab / markdown rendering, crashing the full LocalConversationPage.

Impact

This makes multiple existing conversations unusable. The user cannot reliably reopen important historical threads, and normal app usage is blocked because clicking affected conversations crashes the page.

Request

Please fix the Codex Desktop renderer so invalid or unexpected historical source/review/markdown content is isolated instead of crashing the whole conversation page. A fallback rendering path for unparsable source snippets would unblock affected users.

Additional information

No response