Codex only allows archiving tasks, but there is no way to permanently delete them #1442
Replies: 22 comments 9 replies
|
yes |
|
Please do not forget the “Delete all” button. |
|
Agree! But then they can't scrape that data for training AI! I mean, they probably would just cache it anyway, but I was trying to reason why they'd forget such an obvious thing, lol. |
You're right, having a "Delete" option would help users keep their workspace organized |
|
codex anyway is lame for complex stuff vs gpt 5 |
|
Still, the "delete" option isn't available! |
|
they want to spy on you |
|
reminds me of zed ide, what I did was "rm -rf /Users/user_account/.codex/sessions/2025/*" because wow |
|
I can’t believe it’s still impossible to delete a task — such a basic feature. |
|
If this is a feature you'd like to see, please open a feature request. This is a discussion forum, so mentions of a feature here is likely to go unnoticed by the codex team. |
|
Came here to say this as well! |
|
Is this not a GDPR breach? |
|
If you came here from google, here's the link to the existing feature request, go upvote it #7727 |
|
this is one of the most basic features except there's a behind the scenes u not letting us know |
|
I guess until they add it as a supported options, a Delete All could be: |
|
so easy. |
npx ai-chat-cleaner@latestI've created a CLI tool, but I've only tested it on macOS. Feel free to try it out if you're interested.
|
|
I’m also running into this in Codex desktop. Archive is not enough when a thread was started from the wrong workspace/project and then sticks to that project in the left sidebar. What’s missing for me is both: 1) permanent delete, and 2) reassign/move thread to another workspace. I’ve hit this multiple times already, and misc/system chats end up polluting real project sidebars. |
|
Go into ~/.codex/sessions and you have all the jsonl files of your chats broken by year/month/day. If you delete them there, they clean up the UI logs in archive if oyu can find the right chat |
|
IMO no straight forward delete option is really ridiculous from user perspective. I can't think of a reason. What design decision is behind this? |
|
I skipped purchasing Codex because I couldn't find a way to delete cloud projects. That felt like a significant limitation and raised privacy and data-retention concerns. Until then, I'd recommend being extra careful not to accidentally include secrets, API keys, credentials, or other sensitive information in a project. Without a delete option, users have limited control over removing cloud project history, which is an important capability for privacy and security. Don't buy and use codex |
|
That's honestly a bit scary... I don't even know which part is worse: the fact that you don't know your own folder structure and can't manually perform what would take, at most, four clicks... or the fact that since 2025 someone has documented this huge problem (or MVP feature request) and still hasn't told their own Codex/ChatGPT tool what the problem is so it could solve it for them. Smart tools, smart AI... but what about smart people? 😄 If this was intentionally meant to be a rant thread, then geeez, my bad. |

Uh oh!
There was an error while loading. Please reload this page.
Hi team! Currently, Codex only allows archiving tasks, but there is no way to permanently delete them — even archived ones. Please consider adding a "Delete" option to help users keep their workspace clean and organized. Thanks a lot!
All reactions