Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix VS Code Codex extension hangs when opening previous thread; thread state broadcasts have no handler [2 comments, 3 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#20208•Fetched 2026-04-30 06:31:57
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
1
Author
BrimborionIncBrimborionInc
Participants
antonio-amore-akikiantonio-amore-akikiBrimborionIncBrimborionIncgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×2
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

Unknown

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Opening a previous task thread from history hangs indefinitely. New threads work.

This seems to affect longer threads. I don’t have direct proof of causation, but every thread I’ve seen fail to open had previously gone through a “compacting content” step at least once. Shorter threads that did not compact appear unaffected.

Regression timing: observed after GPT-5.5 release/update. Unexpected behavior: previous thread shows model changed from GPT-5.5 to GPT-5.4 without user action. Expected: previous thread history should hydrate and allow follow-up messages.

Relevant log lines: [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed [IpcClient] Received broadcast but no handler is configured method=thread-read-state-changed Request failed ... method=plugin/list ... Invalid request: AbsolutePathBuf deserialized without a base path

What steps can reproduce the bug?

Start or use a long-running conversation thread. Continue using it until the app performs a “compacting content” step. Leave the thread, refresh, or return to the thread list/history. Try to reopen that same thread. Observe that the thread fails to open or does not load correctly. Compare against a shorter thread that has not gone through compacting; those appear to open normally.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue may be related to the "compacting content" step and the change in GPT model version, and a potential fix could involve investigating the thread-stream-state-changed and thread-read-state-changed broadcast handlers.

Guidance

  • Investigate the IpcClient logs to understand why no handler is configured for the thread-stream-state-changed and thread-read-state-changed methods.
  • Verify if the issue is specific to threads that have gone through the "compacting content" step by testing with multiple threads of varying lengths.
  • Check the plugin configuration and the AbsolutePathBuf deserialization to ensure it is correctly handling the base path.
  • Test if the issue persists when using a shorter thread that has not undergone compacting to isolate the cause.

Example

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

Notes

The issue seems to be related to the GPT-5.5 release/update, and the change in GPT model version from 5.5 to 5.4 without user action may be a contributing factor. However, more information is needed to determine the root cause.

Recommendation

Apply workaround: Given the uncertainty around the root cause, it's recommended to apply a workaround, such as avoiding the "compacting content" step or using shorter threads, until a more permanent fix can be implemented.

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…
#callback error#memory management#API rate limit#retriever error#indexing 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 VS Code Codex extension hangs when opening previous thread; thread state broadcasts have no handler [2 comments, 3 participants]