Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix After VS Code restart/reload, the first Codex history session I click fails to render. [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20192•Fetched 2026-04-30 06:32:21
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
aoaoaoao-wuaoaoaoao-wu
Participants
aoaoaoao-wuaoaoaoao-wugithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

26.422.71525

What subscription do you have?

plus

Which IDE are you using?

cursor

What platform is your computer?

OS: Microsoft Windows NT 10.0.26200.0 x64 PowerShell: 5.1.26100.8115, Desktop edition VS Code: 1.109.5, 072586267e68ece9a47aa43f8c108e0dcbf44622, x64 Cursor: 3.2.16, 3e548838cf824b70851dd3ef27d0c6aae371b3f0, x64

What issue are you seeing?

After restarting or reloading VS Code/Cursor, the first Codex history session I click fails to render its chat history.

The issue is order-dependent, not tied to a specific conversation.

For example, if I open session A first after startup, session A stays blank / does not lo

<img width="1343" height="1397" alt="Image" src="https://github.com/user-attachments/assets/376a3b77-a4c5-4bfd-a15f-8ce7c2c05123" />

ad. If I then open session B, session B loads normally. If I close session B and try session A again, session A still does not load until I restart VS Code/Cursor.

After restarting VS Code/Cursor and changing the order, if I open session B first, then session B fails, while session A can load if opened second.

So the broken session is always the first history session opened after extension startup, and it remains stuck until the editor is restarted.

Expected behavior:

Any Codex history session should load normally regardless of whether it is opened first or second after extension startup.

Actual behavior:

The first clicked history session after extension startup becomes stuck and remains unloadable until VS Code/Cursor is restarted. The affected session changes depending on opening order.

Relevant logs:

maybe_resume_success conversationId=... latestTurnStatus=completed markedStreaming=true turnCount=67

[IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
[IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed

### What steps can reproduce the bug?

1. Restart or reload VS Code/Cursor.
2. Open Codex.
3. Click a Codex history session, for example session A.
4. Observe that session A stays blank / does not load its chat history.
5. Click another history session, for example session B.
6. Observe that session B loads normally.
7. Close session B.
8. Try to open session A again.
9. Observe that session A still does not load.
10. Restart or reload VS Code/Cursor.
11. Open session B first this time.
12. Observe that session B now fails, while session A can load if opened second.

### What is the expected behavior?

Any Codex history session should load its chat history normally after VS Code/Cursor starts or reloads.

The first clicked history session should behave the same as the second and later clicked sessions. Opening order should not affect whether a session can be restored.

If the backend successfully resumes a conversation, the UI should render the restored chat history or retry/rehydrate the session instead of leaving the panel blank.

### Additional information

_No response_

extent analysis

TL;DR

The issue might be related to the handling of the first Codex history session after VS Code/Cursor startup, and a potential workaround could involve modifying the session loading order or the IPC client configuration.

Guidance

  • Investigate the IPC client configuration to ensure it is properly handling the thread-stream-state-changed method, as the logs indicate no handler is configured for this method.
  • Verify that the maybe_resume_success conversationId is correctly associated with the first clicked history session, and that the latestTurnStatus is indeed completed.
  • Check if there are any differences in the way the first and subsequent history sessions are loaded, and if there are any specific conditions that cause the first session to fail.
  • Consider adding a retry mechanism or a fallback to rehydrate the session if the initial load fails.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue seems to be related to the interaction between the VS Code/Cursor extension and the Codex history sessions. The provided logs and steps to reproduce the bug suggest that the problem lies in the handling of the first history session after startup. However, without more information about the extension's code and configuration, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Modify the IPC client configuration to properly handle the thread-stream-state-changed method, and consider adding a retry mechanism to rehydrate the session if the initial load fails. This might help resolve the issue with the first clicked history session after VS Code/Cursor startup.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#runtime error#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix After VS Code restart/reload, the first Codex history session I click fails to render. [1 comments, 2 participants]