codex - 💡(How to fix) Fix Codex VS Code extension fails to enable realtime_conversation; new chats cannot switch model and Output is flooded with worker warnings [1 comments, 2 participants]

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. [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 [warning] worker_rpc_response_error error={} method=stable-metadata workerId=git

• Output shows unsupported feature enablement error

TL;DR

The issue can be resolved by ensuring the Codex extension and local backend are compatible and resetting any stale local state or cache that may be causing the client to request unsupported feature enablement.

Guidance

• Verify that the Codex extension version is compatible with the local Codex backend/app-server to ensure feature support alignment.
• Check for any stale local state or cache that might be causing the client to request the unsupported realtime_conversation feature and consider resetting or clearing it.
• Since the issue persists even in a non-Git project and after downgrading the extension, focus on the compatibility and state/cache aspects rather than the Git worker warnings as a primary cause.
• Inspect the Codex logs further for any patterns or additional errors that could indicate a specific mismatch or configuration issue.

Example

No specific code snippet is provided as the issue seems to be related to configuration, compatibility, or state management rather than a code-level problem.

Notes

The exact steps to reset local state or cache are not specified in the issue, so this would need to be determined based on the specific extension and backend documentation. Additionally, the repeated Git worker warnings, although likely a secondary effect, should be monitored after addressing the primary issue to ensure they do not indicate another problem.

Recommendation

Apply a workaround by checking and ensuring compatibility between the Codex extension and the local backend, and consider resetting any local state or cache. This approach is recommended because it directly addresses the likely cause of the issue as implied by the error messages and the persistence of the problem across different scenarios.