{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid3jz6m7mprxxicl6xvi34htmxqxjavv6kji62aqdmvuc4iaktayu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnbeebfkv3z2"
  },
  "path": "/t/codex-cloud-needs-real-deletion-not-just-archive-for-developer-session-history/1382259#post_1",
  "publishedAt": "2026-06-02T00:04:52.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hi,\n\nI 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.\n\nFrom what I can see, previous Codex Cloud activity remains visible or accessible in areas such as:\n\n  * `https://chatgpt.com/codex/cloud?tab=code_reviews`\n\n  * `https://chatgpt.com/codex/cloud?tab=all`\n\n\n\n\nThe 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.\n\n## The issue\n\nCodex 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.\n\nArchiving is not deletion.\n\nIn coding workflows, a single Codex session may contain sensitive information such as:\n\n  * Private repository names\n\n  * Project structure\n\n  * File paths\n\n  * Logs\n\n  * Error messages and stack traces\n\n  * Code diffs\n\n  * Prompt contents\n\n  * Implementation details\n\n  * Internal API or system architecture information\n\n  * Accidentally included tokens, keys, environment variables, or secrets\n\n\n\n\nSimply hiding these sessions from the main UI does not match the user expectation of deleting a developer work session.\n\n## Related concern\n\nI 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.\n\nNow, the same concern seems to apply to Codex Cloud sessions.\n\nThere does not appear to be a clear, dedicated, and auditable way to delete old Codex Cloud work history separately from general ChatGPT conversation history.\n\n## Expected behavior\n\nCodex should provide explicit deletion controls for Cloud sessions.\n\nSpecifically, I think users should be able to:\n\n  1. Permanently delete an individual Codex Cloud session.\n\n  2. Delete all archived Codex Cloud sessions.\n\n  3. Delete all Codex Cloud work history separately from regular ChatGPT chat history.\n\n  4. Clearly distinguish “Archive” from “Delete” in the Codex UI.\n\n  5. See the retention status after deletion, such as “scheduled for deletion,” “deleted,” or “retention period ending on [date].”\n\n  6. Disable long-term storage of Codex Cloud session history by default or through a user setting.\n\n  7. Use a temporary or private Codex work mode where sessions are not retained beyond the minimum operational period.\n\n\n\n\n## Actual behavior\n\nCurrently, previous Codex Cloud sessions continue to appear as archived conversations or work history.\n\nWith 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.\n\nFor a developer tool, this is a higher-risk default than ordinary chat history because Codex sessions may contain project-specific and security-sensitive information.\n\n## Why this matters\n\nCoding assistant work history should be treated as sensitive developer data, not just ordinary chat content.\n\nArchive 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.\n\nThis 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.\n\n## Question\n\nIs there currently a way to permanently delete Codex Cloud code review history or work session history, rather than just archiving it?\n\nIf not, could Codex add dedicated controls for:\n\n  * Deleting individual sessions\n\n  * Deleting all archived sessions\n\n  * Deleting all Codex Cloud history\n\n  * Managing Codex history separately from regular ChatGPT history\n\n  * Verifying deletion or retention status\n\n  * Using a temporary or private Codex work mode\n\n\n\n\nAs 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.",
  "title": "Codex Cloud needs real deletion, not just archive, for developer session history"
}