VSCode Codex extension 'Failed to delete task' error message
Resolved 💬 40 comments Opened Sep 14, 2025 by MrGeRoI Closed Nov 3, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.4.6
Which model were you using?
gpt-5
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What steps can reproduce the bug?
Create any conversation in Codex inside VSCode and then click on remove task icon
What is the expected behavior?
Removed task
What do you see instead?
<img width="622" height="373" alt="Image" src="https://github.com/user-attachments/assets/ec24595c-6cb5-4535-b958-f9605fd76827" />
40 Comments
Also have this bug.
Tried to re-install codex extension and do all the usual, no dice.
<img width="324" height="55" alt="Image" src="https://github.com/user-attachments/assets/fb6128bd-f062-488e-8a85-a0b62c32dd11" />
You can manually remove the tasks here:
C:\Users\ <user> \.codex\sessions\...
Same here :/
<img width="579" height="114" alt="Image" src="https://github.com/user-attachments/assets/d38c1834-8d30-431f-b592-26d16db842a8" />
I also can not delete any of my tasks in VScode with Codex extension.
confirmed
same here!
nothing in output or problems.
Same here
same here!!
+1 Same here.
111
+1
+1
+1
+1
+1
pre-release version also have this issue
same
+1
+1
The only way I found is to go into Users.codex\session and manually delete the tasks by moving them to another file, then close Cursor, reopen it, and check in the codex section which tasks have been removed.
same
same
same
+1
I, too facing the same issue.
Environment: Microsoft windows 11
VSCode: 1.105.0
Codex : 0.4.19
Please suggest a workaround at least.
<img width="290" height="159" alt="Image" src="https://github.com/user-attachments/assets/2f1ed08a-954a-438b-b795-2ffeee153367" />
same
no one following up on this issue? ？？
I try to fix it myself, but I couldn't find the GitHub repository for this plugin.
anyone know?
+1
same here
same
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
Thanks for the bug report. This will be addressed in the next release.