›_ Codex Issues
Codex Issues / #18842

Codex VS Code extension fails to enable realtime_conversation; new chats cannot switch model and Output is flooded with worker warnings

Open 💬 4 comments Opened Apr 21, 2026 by ranaguir
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

26.417.40842

What subscription do you have?

Plus

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Summary

After opening Codex in VS Code, new chats do not allow changing the model, while existing chats still do. The Output panel shows a preceding JSON-RPC error indicating that the client tries to enable realtime_conversation, but the backend reports that this feature is unsupported. After that, repeated git worker warnings appear, even in a non-Git project.

Environment
VS Code
Codex extension
Windows
Non-Git workspace
Problem persists even after downgrading the extension version

Logs
[error] Request failed conversationId=none durationMs=482 error={"code":-32600,"message":"unsupported feature enablement realtime_conversation: currently supported features are apps, plugins, tool_search, tool_suggest, tool_call_mcp_elicitation"} id=0115cca7-a39c-45c8-8d54-aad71c71af42 method=experimentalFeature/enablement/set pendingCountAfter=8 timeoutMs=0

Then repeatedly:

[warning] worker_rpc_response_error error={} method=stable-metadata workerId=git

What steps can reproduce the bug?

Steps to reproduce

  1. Open VS Code in a non-Git folder
  2. Open Codex
  3. Create a new chat
  4. Try to change the model
  5. Observe that model switching does not work in the new chat
  6. Open Output panel and inspect Codex logs

Actual behavior

  • New chats cannot change model
  • Existing chats can change model
  • Output shows unsupported feature enablement error
  • Then Output is flooded with repeated git worker warnings

What is the expected behavior?

Expected behavior

  • New chats should initialize correctly
  • Model switching should work consistently
  • Client should not attempt to enable unsupported features, or should gracefully fall back
  • No repeated worker warnings in Output

Additional information

  • The issue persists after reverting to a previous extension version
  • Workspace is not using Git
  • This suggests either a capability mismatch between the extension and local Codex backend/app-server, or stale local state/cache causing the client to request unsupported feature enablement

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

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

  • #18515
  • #17394
  • #18775

Powered by Codex Action

iamjohnnymac · 4 months ago

Same issue on the Windows Desktop app (MSIX, OpenAI.Codex 26.421.620.0, Win 11 24H2). UI never renders — stuck on splash logo indefinitely. Log floods with unsupported feature enablement \realtime_conversation`` at hundreds of requests per minute (200+ MB of logs in minutes), renderer eventually mounts routes after ~355 seconds but app remains unusable. Killing processes is the only way to recover.

trefrog · 4 months ago

fwiw, ChatGPT says, after many volleys and log viewing:

Workspace/multi-root was causing the Git metadata spam. Opening a single folder stops that piece, so the stable-metadata workerId=git hammering was probably Codex stumbling over one of the workspace roots, or one repo without a remote, or the workspace structure itself. The remaining breakage is service/auth/extension-side. The big log showed the Codex app-server successfully starting, then getting bounced by a Cloudflare-style 403 on chatgpt.com/backend-api/plugins/featured?platform=codex, plus the earlier Server overloaded failures. That is not explained by Git anymore.

Codex CLI is working perfectly for me, and I'm able to get some action in the VS Code extension, but it's a SLOW syrup drip.

DigitalAndSEO · 4 months ago

I’m seeing what looks like a related issue on macOS with the latest VS Code extension.

Environment

  • Codex / ChatGPT VS Code extension: openai.chatgpt@26.422.30944
  • VS Code: 1.117.0
  • VS Code arch: arm64
  • OS: macOS 26.4.1 build 25E253
  • Kernel: Darwin 25.4.0 arm64
  • Workspace: Git repo opens correctly; git status works. Remote is currently configured as origin = local-only.

What I see

When I open Codex / ChatGPT in VS Code, the Codex Output panel starts logging repeated Git worker warnings:

[warning] worker_rpc_response_error error={} method=stable-metadata workerId=git

Then I also see repeated 403 Forbidden fetch errors to this endpoint:

[error] Error fetching httpStatus=403 statusText=Forbidden url=https://chatgpt.com/ces/v1/rgstr?...&st=javascript-client-react&sv=3.32.2...

When I open or use a chat, the Output panel is also flooded with IPC warnings like:

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

These warnings appear repeatedly while the conversation is active / streaming.

Example logs

On opening a chat:

2026-04-25 14:51:41.064 [warning] worker_rpc_response_error error={} method=stable-metadata workerId=git
2026-04-25 14:51:41.075 [warning] worker_rpc_response_error error={} method=stable-metadata workerId=git
2026-04-25 14:51:41.213 [info] [git-repo-watcher] Starting git repo watcher
2026-04-25 14:51:47.803 [error] Error fetching httpStatus=403 requestId=REDACTED statusText=Forbidden url=https://chatgpt.com/ces/v1/rgstr?k=REDACTED&st=javascript-client-react&sv=3.32.2&sid=REDACTED&ec=3&gz=1

While chatting / streaming:

2026-04-25 14:52:50.205 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
2026-04-25 14:52:50.232 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
2026-04-25 14:52:50.648 [warning] [IpcClient] Received broadcast but no handler is configured method=thread-read-state-changed
2026-04-25 14:52:56.973 [error] Error fetching httpStatus=403 requestId=REDACTED statusText=Forbidden url=https://chatgpt.com/ces/v1/rgstr?k=REDACTED&st=javascript-client-react&sv=3.32.2&sid=REDACTED&ec=4&gz=1

Notes

The chat itself still appears to work, but the Output panel gets noisy with repeated warnings/errors. This seems related to this issue because of the repeated stable-metadata Git worker warnings, but in my case I also consistently see the ces/v1/rgstr 403 Forbidden errors and the repeated IPC thread-stream-state-changed / thread-read-state-changed warnings.

----

The chat itself still appears to work in some cases, but the Output panel gets noisy with repeated warnings/errors. This seems related to this issue because of the repeated stable-metadata Git worker warnings, but in my case I also consistently see the ces/v1/rgstr 403 Forbidden errors and the repeated IPC thread-stream-state-changed / thread-read-state-changed warnings.

Also, some older chats no longer open correctly. When I try to open them, the chat appears to stay stuck in a loading/thinking state, while the Output panel keeps logging this warning indefinitely:

[warning] worker_rpc_response_error error={} method=stable-metadata workerId=git