Error creating task timeout
Run the Codex CLI in the same project first — reporters consistently find it still works while the extension or app fails, and it often prints the real error the app swallows, typically a malformed config or skill file under ~/.codex. Then start a fresh thread instead of resuming an old one (the timeout variant clusters in old threads), restart or reinstall the extension, and check status.openai.com. Both tracking issues remain open; no confirmed upstream fix.
Affected versions: reports span extension 0.4.74–0.5.74, CLI 0.72–0.101, and desktop builds, Dec 2025–May 2026; no fixed-in version identified
Error creating task is a whole family of failures wearing one generic string — reported variants include timeout, no rollout found for thread id, and plain Error starting conversation. The pattern that runs through nearly every report: the Codex CLI keeps working in the same project while the IDE extension, desktop app, or cloud task fails.
Symptoms
- Sending a prompt in the VS Code extension fails instantly with
Error creating taskorError starting conversation, in a project that worked two days earlier and still works in the CLI. - The
timeoutvariant hits when prompting inside an old thread — two reporters in April 2026 say new threads work fine while resumed ones fail. - On cloud, the failure reads
Failed to Create TaskorFailed to Create Follow-Up, documented in a July 2025 forum thread. - On the desktop app, users report a crash followed by persistent task-creation failures that survive restarts.
Cause
OpenAI has not published a single root cause, and both tracking issues remain open. Individual cases have been traced, though. The #9001 reporter found a SKILL.md file with invalid YAML under ~/.codex/skills/ — the CLI printed the parse error, while the extension failed silently, and an OpenAI maintainer agreed the extension should surface a better error instead. Another commenter hit the same wall from invalid TOML in ~/.codex/agents/*.toml. The July 2025 cloud wave was service-side, recovering within the hour for many users. The app layer chokes on unparseable local config, stale thread state, or a service incident, and reports all three with the same string.
Fix
- Run the CLI in the same project. If
codexworks, the fault is the app layer; if it errors, read the output — the CLI surfaced the parse error behind the original #9001 report. - Check
~/.codexfor recently edited config. Broken YAML in aSKILL.mdor broken TOML inagents/*.tomlboth reproduce this. Recent AGENTS.md edits are worth checking too. - Start a fresh thread. The timeout variant clusters in resumed threads.
- Restart, then reinstall, the extension or app. A restart was the maintainer’s first suggestion, one commenter fixed it with a VS Code restart, and another by reinstalling the extension.
- Check status.openai.com. The cloud variant has been an outage before.
- Still stuck? Run
/feedbackto upload logs and post your thread ID on #9001 — maintainers ask reporters for both.
Affected versions
Reports span extension versions 0.4.74 through 0.5.74, CLI 0.72 through 0.101, and desktop builds, from December 2025 into May 2026; an April 2026 comment says it still happened on the latest version. No release note marks this class fixed; we’ll update this page when one does.
Facts on this page verified July 15, 2026.
- openai/codex #9001 — 'Error creating task or Error starting conversation' (open)
- openai/codex #8022 — 'Error Creating Task' (open)
- OpenAI community forum — 'Error creating task' error in Codex App
- OpenAI community forum — Codex failing to create new tasks and follow-ups
- openai/codex issue tracker — 'error creating task' reports