VSCode extension: "no rollout found" error on every new conversation (ChatGPT Plus, Windows 10) #11997

Description

The Codex VSCode extension fails to create or resume any conversation, returning "no rollout found for thread id ..." on every attempt, including brand-new conversations. The Codex CLI works perfectly with the same authentication.

Environment

• OS: Windows 10 Home 10.0.19045
• VSCode: 1.109.3 (x64)
• Extension: openai.chatgpt v0.4.74
• Codex CLI: v0.101.0 (works fine)
• Node.js: v24.13.1
• Plan: ChatGPT Plus
• Auth mode: ChatGPT login (browser-based)
• Model: gpt-5.2-codex (also tried gpt-5.3-codex — same error)
• No WSL installed

Steps to Reproduce

1. Install Codex extension in VSCode on Windows 10
2. Sign in with ChatGPT Plus account
3. Open any project folder
4. Try to start a new conversation → "Error creating task"

What happens

A login screen briefly flashes inside the Codex panel, then disappears, and the error appears. This happens on every attempt, even after:

• Full logout + re-login (codex logout / codex login)
• Clearing all sessions (~/.codex/sessions/, ~/.codex/archived_sessions/)
• Deleting VSCode workspace state (state.vscdb)
• Deleting models cache
• Killing all codex.exe processes
• Complete uninstall + reinstall of extension
• Switching models (gpt-5.2-codex ↔ gpt-5.3-codex)

The CLI works perfectly with codex exec "..." using the same auth tokens.

Extension Logs

2026-02-17 15:33:27.743 [info] Activating Codex extension
2026-02-17 15:33:27.743 [info] [CodexMcpConnection] Spawning codex app-server
2026-02-17 15:33:28.409 [info] [CodexMcpConnection] Initialize received (id=1)
2026-02-17 15:33:31.753 [error] [CodexWebviewProvider] Error fetching conversation summary: {"code":-32600,"message":"no rollout found for conversation id 019c6bce-5a18-7141-b76d-8fd887cf75a1"}
2026-02-17 15:33:34.903 [error] Request failed conversationId=019c6bce-5a18-7141-b76d-8fd887cf75a1 durationMs=687 error={"code":-32600,"message":"no rollout found for thread id 019c6bce-5a18-7141-b76d-8fd887cf75a1"} method=thread/resume
2026-02-17 15:33:34.904 [error] Failed to resume conversation conversationId=019c6bce-5a18-7141-b76d-8fd887cf75a1
2026-02-17 15:33:45.482 [error] [Composer] submit failed cwd=c:\Users\ASUS\OneDrive\דוקטורט error={} followUp=local mode=local

Key Observation

The conversation ID (019c6bce-...) is new — generated fresh after clearing all local state. The server itself returns "no rollout found" for brand-new threads. This is not a stale session issue — it's a server-side rollout/feature-flag issue for this account.

Related Issues

• JetBrains (IntelliJ IDEA) ACP / Codex: AI Chat becomes unusable after using gpt-5.3-codex; session/resume fails with “no rollout found for thread id …” and persists even after switching back to gpt-5.2-codex #11693 — same "no rollout found" error with gpt-5.3-codex on JetBrains
• Codex VS Code extension stopped working overnight with ChatGPT login (Plus user) #11287 — Codex VSCode extension stopped working for Plus user
• "Failed to resume task" when trying create "New Codex Agent" #11727 — "Failed to resume task" when creating new conversations

Expected Behavior

The extension should create a new conversation and allow interaction, just like the CLI does with the same auth credentials.