Codex VS Code extension lists chats that cannot be opened

Open 💬 2 comments Opened Apr 30, 2026 by elettronica67

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.422.71525

What subscription do you have?

Business

What platform is your computer?

Windows 11

What issue are you seeing?

The Codex VS Code extension shows multiple existing chats/conversations in its chat list, but many of them cannot be opened. These chats are displayed by the extension itself, but selecting them does not load the conversation.

What steps can reproduce the bug?

Open VS Code.
Open the Codex extension panel.
Look at the listed existing chats/conversations.
Click one of the affected chats.
Observe that the chat does not open or does not load.

What is the expected behavior?

Every chat listed by the Codex VS Code extension should either open correctly or be hidden/marked unavailable with a clear error message.

Additional information

Please let me know which logs would be useful; I can provide sanitized VS Code/Codex extension logs.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#20131
#18993
#20208
#20197
#19144

Powered by Codex Action

gitman2015 · 4 months ago

I can reproduce this on Windows 10 Pro with the VS Code Codex extension version 26.422.71525.

Issue:

the extension lists existing chats/conversations
some of them cannot be opened
clicking them does not load the conversation content

This does not look like a simple "missing data" case, because the sessions are listed by the extension itself.

Relevant Codex output/log lines:

These warnings appeared while I was trying to open existing conversations:

2026-04-30 12:54:00.056 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
2026-04-30 12:54:07.454 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-read-state-changed

I saw the same pattern again later:

2026-04-30 13:04:40.744 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
2026-04-30 13:04:40.745 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-read-state-changed

This suggests that thread/session events are arriving, but the extension UI has no handler configured for them, which may explain why listed chats fail to load.

I also saw startup-time feature sync errors:

2026-04-30 12:35:17.112 [error] Request failed ... error={"code":-32600,"message":"unsupported feature enablement `workspace_dependencies` ..."} method=experimentalFeature/enablement/set
2026-04-30 12:35:17.113 [error] Failed to sync experimental feature enablement error={"code":-32600,"message":"unsupported feature enablement `workspace_dependencies` ..."} hostId=local

This may indicate a version/feature mismatch between the VS Code extension and the local Codex app-server.

I also saw nearby 403 errors on analytics/registration endpoints, for example:

/backend-api/codex/analytics-events/events
/ces/v1/rgstr

These may be related, but they seem less directly tied to chat loading than the repeated thread-event handler warnings.

I also saw Server overloaded; retry later. errors, for example on connector logo endpoints such as:

2026-04-30 12:35:30.823 [error] Error fetching error={"code":-32001,"message":"Server overloaded; retry later."} url=/aip/connectors/asdk_app_6948a6ade0148191a5da87f9e4b6c3dd/logo?theme=light

This may indicate some broader backend instability at the time, but in my logs these overload errors appeared on connector/logo endpoints rather than clearly on chat-loading endpoints, so I cannot tell whether they were directly related to the conversation loading failure.

Additional note:

reinstalling the extension did not look like a reliable long-term fix