Codex Cloud needs real deletion, not just archive, for developer session history

Codex
,
1

Hi,

I would like to ask whether there is currently a way to actually delete Codex Cloud code review and work session history, instead of simply archiving it.

From what I can see, previous Codex Cloud activity remains visible or accessible in areas such as:

  • https://chatgpt.com/codex/cloud?tab=code_reviews

  • https://chatgpt.com/codex/cloud?tab=all

The current behavior appears to be closer to archiving. However, what I am looking for is not just a way to hide or organize old sessions, but a way to delete the Codex Cloud session history that remains associated with my account.

The issue

Codex Cloud sessions appear to remain as archived conversations or work history even after they are no longer actively used. For a developer tool, I think this creates an important privacy and data retention concern.

Archiving is not deletion.

In coding workflows, a single Codex session may contain sensitive information such as:

  • Private repository names

  • Project structure

  • File paths

  • Logs

  • Error messages and stack traces

  • Code diffs

  • Prompt contents

  • Implementation details

  • Internal API or system architecture information

  • Accidentally included tokens, keys, environment variables, or secrets

Simply hiding these sessions from the main UI does not match the user expectation of deleting a developer work session.

Related concern

I have previously noticed a similar issue with local Codex state files, where chat or session data stored under paths such as .codex could not be clearly managed or deleted through an obvious user-facing flow.

Now, the same concern seems to apply to Codex Cloud sessions.

There does not appear to be a clear, dedicated, and auditable way to delete old Codex Cloud work history separately from general ChatGPT conversation history.

Expected behavior

Codex should provide explicit deletion controls for Cloud sessions.

Specifically, I think users should be able to:

  1. Permanently delete an individual Codex Cloud session.

  2. Delete all archived Codex Cloud sessions.

  3. Delete all Codex Cloud work history separately from regular ChatGPT chat history.

  4. Clearly distinguish “Archive” from “Delete” in the Codex UI.

  5. See the retention status after deletion, such as “scheduled for deletion,” “deleted,” or “retention period ending on [date].”

  6. Disable long-term storage of Codex Cloud session history by default or through a user setting.

  7. Use a temporary or private Codex work mode where sessions are not retained beyond the minimum operational period.

Actual behavior

Currently, previous Codex Cloud sessions continue to appear as archived conversations or work history.

With the current behavior, it is easy for a user to assume that a previous session has been cleaned up or is no longer retained, when in reality it still appears to remain associated with the account.

For a developer tool, this is a higher-risk default than ordinary chat history because Codex sessions may contain project-specific and security-sensitive information.

Why this matters

Coding assistant work history should be treated as sensitive developer data, not just ordinary chat content.

Archive is useful for organization, but it is not a privacy or security control. Users need a clear way to delete previous Codex Cloud sessions and verify that those sessions are no longer retained in their account history.

This is especially important because Codex may interact with private repositories, local development environments, logs, stack traces, dependency information, and internal implementation details. If this data remains in long-term session history, it can create security, privacy, and compliance concerns for individual developers, companies, and teams.

Question

Is there currently a way to permanently delete Codex Cloud code review history or work session history, rather than just archiving it?

If not, could Codex add dedicated controls for:

  • Deleting individual sessions

  • Deleting all archived sessions

  • Deleting all Codex Cloud history

  • Managing Codex history separately from regular ChatGPT history

  • Verifying deletion or retention status

  • Using a temporary or private Codex work mode

As Codex becomes more deeply integrated into developer workflows, deletion and data retention controls for Cloud sessions feel like essential security features, not just convenience features.

2

Hi @zorimo, welcome to the OpenAI community!

Appreciate you sharing the pain point and the behavior you were expecting.

Could you check the Archived Chats section and see if you're able to delete them from there?

- Avinash

3

Sorry to chime in! But I just checked the Archived Chats section and I don’t see a delete option there either. The only available action seems to be “Unarchive.”

So I think the concern is still: the archive does not appear to function as deletion.

I would also love to hear clarification on Codex’ privacy/data retention. If deletion becomes available later (hopefully soon), would Codex Cloud session history follow the same deletion policy as ChatGPT conversations (deletion after 30 days retention period). Or does Codex Cloud work history have a separate policy? (and if so, where to read it).

Thank you.

4

Hi @zorimo, thanks for checking. Could you please share your device details and operating system, also it it a web or an app?

As for your question, it's still under discussion at the moment.

5 
I did some digging through the current public OpenAI docs, and I think this issue would benefit from a clearer official answer.

## What the public docs seem to say

1. **ChatGPT chats support deletion, not just archive.**  
   OpenAI’s Help Center says deleted chats are removed from chat history immediately and scheduled for permanent deletion from OpenAI systems within 30 days, unless legal/security/de-identification exceptions apply. It also says archived chats remain in the account and archive is not deletion.  
   https://help.openai.com/en/articles/8809935-how-to-delete-and-archive-chats-in-chatgpt

2. **Codex docs currently document archive/unarchive, but I could not find delete.**  
   Codex app docs mention finding, continuing, pinning, or archiving a thread. The archived threads section mentions Unarchive, but I did not see a documented Delete control for Codex threads.  
   https://developers.openai.com/codex/app/features  
   https://developers.openai.com/codex/app/troubleshooting

3. **Codex app-server docs also appear to expose archive/unarchive, not delete.**  
   The documented thread APIs include `thread/archive` and `thread/unarchive`, but I did not see a documented `thread/delete` equivalent.  
   https://developers.openai.com/codex/app-server

4. **Codex training/data controls depend on plan type.**  
   OpenAI’s Codex Help article says ChatGPT training data controls apply to whether content processed through Codex may be used to improve OpenAI’s models. It also says Business, Enterprise, and Edu data is not used for model improvement by default, while Pro and Plus conversations may be used unless training is disabled in ChatGPT data controls.  
   https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan

5. **OpenAI’s general Terms say content may be used to provide, maintain, develop, and improve services, with an opt-out for model training.**  
   https://openai.com/policies/terms-of-use/

6. **OpenAI’s business privacy page says business data is not used for training by default.**  
   https://openai.com/business-data/

## What still seems unclear

I could not find a public OpenAI doc that explains whether Codex Cloud session history follows the same deletion policy as normal ChatGPT chats, or whether it has a separate retention/deletion model.

I also could not find a public doc explaining why Codex Cloud sessions appear to support archive/unarchive but not explicit deletion.

## Clarification requested

Could OpenAI clarify:

1. Are Codex Cloud sessions covered by the same deletion policy as ChatGPT chats?
2. If yes, where is the user-facing deletion control for individual Codex Cloud sessions?
3. If no, what retention policy applies specifically to Codex Cloud session history?
4. Are archived Codex Cloud sessions eligible for model training for Plus/Pro users unless training is disabled?
5. Is there currently any way to permanently delete individual Codex Cloud sessions, all archived Codex Cloud sessions, or all Codex Cloud history?
6. If deletion is not currently available, is this a product limitation, a retention/compliance requirement, or something still under design?

The main concern is that archive is documented as “not deletion” for ChatGPT chats, while Codex Cloud sessions can contain especially sensitive developer data: repository names, file paths, diffs, logs, stack traces, prompts, and accidental secrets. A clear deletion and retention policy for Codex Cloud would be very helpful.
6

Before responding to @DevDragon14, I wanted to add that archived chats can be deleted in the Windows app, you can try Settings → Settings → Archived Chats → Delete All

That said, I’ve only tested this on Windows, so the steps or availability may differ on other platforms. Can someone confirm this?

Avinash

7

Hi,

Thanks for your patience, and thanks for looking into this.

Here are my environment details:

  • Device: Windows PC

  • Operating system: Windows 11

  • Client: Web browser

  • Not using a Codex app

  • Relevant URLs:

    • https://chatgpt.com/codex/cloud

    • https://chatgpt.com/codex/cloud?tab=code_reviews

I checked the Archived Chats section as suggested, but my concern is specifically about Codex Cloud session history and Codex code review history. From what I can see, these Codex Cloud records still appear to be managed separately from regular ChatGPT archived chats.

The main issue is that I can find ways to hide/archive or navigate previous Codex Cloud sessions, but I cannot find a clear way to permanently delete the Codex Cloud session history itself.

Thanks for confirming that this is still under discussion. I think having a dedicated delete flow for Codex Cloud history would be very helpful, especially because these sessions may contain repository names, file paths, logs, diffs, implementation details, and other developer-sensitive context.

Please let me know if there is any additional information I can provide.

Thank you.

8

I see the pain point here.

I’ll surface this to product engineering so they can look into a clearer way to permanently delete Codex cloud session history.

Appreciate you for expanding on this.

Avinash

9

Hi Avinash,

Thank you for acknowledging the request and for surfacing it to product engineering.

If there is any update on this in the future, it would be great if the related release note, changelog, or product update could be shared here as a comment as well. I think this would be helpful not only for me, but also for other developers who may have the same concern around Codex Cloud session history and data retention.

I’d also be happy to continue providing feedback if it helps improve the Codex developer experience.

Thanks again, and have a great day!