"Failed to resume task" when trying create "New Codex Agent"

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

• #11721

Powered by Codex Action

Hi, I reviewed '"Failed to resume task" when trying create "New Codex Agent"' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.

Same issue here. Extension 0.4.74, VS Code Remote SSH to Ubuntu 24.04. Sidebar works, tab/command palette shows "Failed to resume task." Tested with two different OpenAI accounts, fresh installs on both client and server sides. Reproduced from both Windows 11 and macOS clients — not Windows-specific.

Additional troubleshooting attempted, all with the same result:

• Wiped ~/.vscode-server and ~/.codex on the remote server
• Complete uninstall/reinstall of VS Code client and all extensions
• Tried pre-release version 0.5.74
• Switched from the bundled Codex binary to the latest npm global install (@openai/codex)

None of the above resolved the issue. Only the sidebar icon reliably starts a new thread.

Relevant output from the Codex output channel:

[error] Error fetching {}: {} templateArgs=["vscode://codex/local-environments",{}]
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
[error] [CodexWebviewProvider] Error fetching conversation summary: {} templateArgs=[{"code":-32600,"message":"no rollout found for conversation id <redacted>"}]
[error] Request failed conversationId=<redacted> error={"code":-32600,"message":"no rollout found for thread id <redacted>"} method=thread/resume
[error] Failed to resume conversation error={"code":-32600,"message":"no rollout found for thread id <redacted>"}

The root cause appears to be thread/resume attempting to resume a non-existent thread when opening a new agent tab, returning "no rollout found for thread id".

Also potentially related to #11721 — I also had multiple VS Code Remote SSH sessions open to the same host at one point, though unclear if that's a trigger or coincidence.

Having same error on windows when clicking on new codex session

Same issue here using Cursor on macOS and WSL.

New agents fail to start when logged in with "failed to resume task".
Existing tasks also never resume after IDE restart.

Temporary workaround: log out, create a new agent, then log in again inside the new agent.

In the mean time, you can revert to 0.4.71 which is unaffected by this bug:

1. Open Extensions and click Codex
2. Click the drop-down menu next to Uninstall and press Install specific version...
3. Choose 0.4.71
4. Restart extensions

Having the same problem, reinstalling extensions, deleting folders and relogging did not work.
Thank you, @stewartadam - can confirm this fixes it. Try restarting vscode again after following the steps if it doesn't work right away. :)

In the mean time, you can revert to 0.4.71 which is unaffected by this bug: 1. Open Extensions and click Codex 2. Click the drop-down menu next to Uninstall and press Install specific version... 3. Choose 0.4.71 4. Restart extensions

when a real fix for this issue will be available, any related PRs?

Same issue Macos vs code, codex extension itself works but there are haging new threads in it. Chat itself completely broken

Still broken on latest prerelease version
MacOS Sequoia 15.7, Cursor 2.4.31

Additional info:
Going back to 0.4.71 does indeed eliminate this problem.
Moving forward to 0.4.73, we can still work in an existing session, but we cannot create a new agent/session.
If we move back from .74 to .73, the issue with an existing session returns. It's only in moving back to .71 and then forward to .73 that an existing session still works. 😕
I'm sticking with .71, but this still has the annoying log issue from #10831 that is not present in .73.
Thanks team!

Спасибо @stewartadam! Ты красавчик

@stewartadam kudos mate

The latest version of the VSCode Codex plugin still has the same error.

Rolling back to version 0.5.72 can resolve the issue.

I suspect that the VSCode plugin for OpenAI Codex CLI is maintained by those technically poor vibe-coders?

My environment:

• Mac mini M4
• VSCode latest

I'm also having this issue but it seems to persist even on 0.4.71. Signing in/out does fix it but only for that window/thread.
Hoping for a fix soon.

• M2 Mac Mini
• VSCodium latest

Extension v0.4.72+ fires thread/resume when opening any new agent tab — if there's no prior thread, the API returns an error that surfaces as "Failed to resume task". Downgrading to v0.4.71 via the Extensions panel fixes it immediately. Steps: https://cacheoverflow.dev/blog/6Pdap9xf

I'm still running 0.4.71 and the current version is ... using the new semver scheme.
Any progress on this? Recommendation for staying back, or moving forward and not using the feature? Thanks.

Just notice that even tho you hit "CHAT" bottom to reach your past session and drag it to a new window, there is a chance that you stuck on "thinking" after sending a new message. I will have to reload everything to get the response shown.

VSCode version:
Version: 1.108.2 (Universal)
Commit: c9d77990917f3102ada88be140d28b038d1dd7c7
Date: 2026-01-21T13:52:09.270Z
Electron: 39.2.7
ElectronBuildId: 12953945
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.6.0

Codex extension:
Version
26.311.21342

Hi all! Sorry about the delay and I am currently looking into the issue.

Hi all! Sorry about the delay and I am currently looking into the issue.

Thanks! This bug has been hit me for a month +. Everytime I updated the VScode plugin and would test whether the bug has been solved —— and failed.

This bug is p0-level and essential. Although I can use Codex Side bar as a temporary way to use the latest version of Codex VSCode Plugin, I do hope this more flexible, powerful way, Codex: New Codex Agent, could be use normally as soon as possible.

Thanks a lot! Looking for your good news!

@shijie-oai, is it closed, but not released yet? Asking because for me, it's still the issue. 26.313.41514
/ 26.5313.41514

Hi all! Sorry about the delay and I am currently looking into the issue.

@shijie-oai

Thanks for the update of version 26.5318.11754 ! This bug had been repaired. However, annother smaller bug appears:

• Click Codex: New Codex Agent, the conversation starts.
• Click Codex: New Codex Agent again, a new conversation should start - but nothing happens.

This feature is important, because sometimes we need multi-conversation in a VSCode project.

Could it be back? Thanks!

Hi all The issue has been fixed in 26.5318.11754 pre-release and matching release. Our linear project too eagerly closely this ticket before the release went out. @huangwb8 will investigate into this and open a new editor panel when there is a split view.

I can confirm its fixed for me but only after using pre-release 26.5323.20928