[WSL/Linux] Long Codex threads intermittently open as blank panel, short threads load normally

What version of the IDE extension are you using?

openai.chatgpt-26.5422.21459-linux-x64 / openai.chatgpt-26.422.21459-linux-x64

What subscription do you have?

GPT PLUS

Which IDE are you using?

Cursor

What platform is your computer?

Linux 5.15.167.4-microsoft-standard-WSL2 x86_64 x86_64

What issue are you seeing?

Long existing Codex conversations intermittently fail to load in the Cursor IDE extension.

Short conversations usually open normally, but longer existing conversations sometimes open as a blank panel or stay stuck loading. The issue is intermittent: the same long conversation may load successfully sometimes, but fail at other times.

I tested both the preview/latest Codex extension and the release version, and the issue still happens. Cursor is already updated to the latest version.

This looks related to Codex IDE extension + Cursor host compatibility and/or long thread replay/hydration.

Relevant logs include:

Codex chat session item provider not registered errorMessage="nt.chat.registerChatSessionItemProvider is not a function" errorName=TypeError

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

WARN codex_app_server::transport: dropping overload response for connection ConnectionId(0): outbound queue is full

worker_rpc_response_error error={} method=stable-metadata workerId=git

I also saw repeated Git worker warnings. However, after fixing the local Git repository state by creating an initial commit, the long conversation loading issue still appears related to the Codex extension / Cursor integration.

What steps can reproduce the bug?

1. Open Cursor with the Codex IDE extension installed.
2. Open the Codex extension panel.
3. Open a short existing Codex conversation.
4. Observe that the short conversation usually loads normally.
5. Open a much longer existing Codex conversation.
6. Observe that the panel sometimes stays blank or stuck loading.
7. Reload the Cursor window and try again.
8. The same long conversation may sometimes load successfully and sometimes fail.

This seems easier to reproduce with long existing threads that contain many turns, tool events, and logs.

What is the expected behavior?

Long existing Codex conversations should load reliably in the Cursor IDE extension, the same as short conversations.

If a required Cursor host API is unsupported, or if the webview / bridge is not ready during thread replay, the extension should fail gracefully with a visible error message instead of leaving the panel blank or stuck loading.

Additional information

Environment:

• IDE: Cursor latest version
• Platform: WSL2 / Linux
• Kernel: Linux 5.15.167.4-microsoft-standard-WSL2
• Codex extension versions tested:
• openai.chatgpt-26.5422.21459-linux-x64
• openai.chatgpt-26.422.21459-linux-x64
• Workspace path: /home/chase_610/cursor/meme_generator

The issue appears similar to:

• https://github.com/openai/codex/issues/18931

I also noticed that on startup the extension logs:

Codex chat session item provider not registered errorMessage="nt.chat.registerChatSessionItemProvider is not a function"

This suggests the extension is calling a Chat Session API that may not exist in the current Cursor host.

When the long thread fails to load, logs also show broadcast / IPC related warnings and app-server backpressure / queue warnings, such as:

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

WARN codex_app_server::transport: dropping overload response for connection ConnectionId(0): outbound queue is full

The behavior is intermittent, which makes it look like a race condition during long thread hydration/replay.