OpenAI Codex CLI error
Codex CLI: Error starting conversation
Error starting conversationStatus: Fixed in releaseLast verified 2 documented fixes3 sources
What it means
The Codex VS Code extension failed as soon as a new chat was started, before any code was involved.
Causes
- Bash detection failure in the VS Code Codex extension on Windows under certain conditions (PR #3421).
How to fix it
- Fix 1.
Update: PR #3421 was merged into extension pre-release 0.5.32 and the next mainline release (maintainer dylan-hurd-oai on #2841); the CLI change first shipped in rust-v0.51.0.
- Fix 2.
Maintainers strongly recommended running in WSL2 on Windows for the best sandbox and approvals experience (#2841).
More Codex CLI errors
All 14 Codex CLI errorsstream disconnected before completion: stream closed before response.completedStatus: Workaroundstream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)Status: OpenError running remote compact task: stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses/compact)Status: Fixed in releaseSelected model is at capacity. Please try a different model.Status: By designYour access token could not be refreshed because your refresh token was already used. Please log out and sign in again.Status: Fixed in releaseCodex ran out of room in the model's context window. Start a new thread or clear earlier history before retrying.Status: Fixed in releaseError logging in: Port 127.0.0.1:1455 is already in useStatus: WorkaroundToken exchange failed: token endpoint returned status 403 ForbiddenStatus: Workaround
Related reading
- Codex Training Setting Re-Enabled? Two Switches to CheckDevelopers report Codex model training turning itself back on. What OpenAI documents, the second "Include environments" switch most people miss, and a five-minute check.
- OpenAI Pando: The Git Backend Built for Codex-Scale PushesOpenAI built Pando, a Git-compatible backend, after Codex flooded its monorepo with pushes. What it changed, the trade-offs, and what it means for your agent fleet.
- T3 Code: Open-Source GUI for Claude Code and CodexT3 Code is a free, MIT-licensed desktop, web and mobile app that drives Claude Code, Codex, Cursor, OpenCode and more. What it is, how remote access works, and what to check first.
- Android Studio Now Runs Claude and Codex: ACP Setup GuideAndroid Studio Rabbit 2 hosts 40+ ACP coding agents, Claude and Codex included, and Android CLI ships as a Claude Code and Codex plugin. Setup and caveats.
- Codex Could Not Start in VS Code: What the Error Means and How to Fix ItCodex shows "The extension could not start its user interface" in VS Code, Remote SSH, Dev Containers and Cursor. Read the log first, then pick the fix that matches.
- GPT-6.1 Terra: $1/$5 Pricing, Benchmarks, and When to Pick ItGPT-6.1 Terra is OpenAI's new $1/$5 per million token model: 50.3% on Terminal-Bench 4.0 (vendor-reported), half Sol's price, and who should route to it.
FAQ
What does "Error starting conversation" mean in Codex CLI?
The Codex VS Code extension failed as soon as a new chat was started, before any code was involved.
How do I fix "Error starting conversation"?
There are 2 documented fixes. Start with the first: Update: PR #3421 was merged into extension pre-release 0.5.32 and the next mainline release (maintainer dylan-hurd-oai on #2841); the CLI change first shipped in rust-v0.51.0.
Is this Codex CLI error fixed?
Status: Fixed in release. A release fixed this. The affected versions note says where the fix landed. Affected versions: Reported on Windows 10 with the new VS Code extension, August 2025 (#2841); fixed in extension 0.5.32 and rust-v0.51.0
Sources
Last verified against 3 sources: official docs, maintainer replies and release notes.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.