openai / openai/codex

[Bug] Archived chats page has no delete option, only “Unarchive”

Open
#39,839 5 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

In the Codex archived chats page, archived conversations cannot be deleted because each row only shows “Unarchive” and there is no visible delete/trash action.

This conflicts with the current OpenAI Help Center guidance for Codex chat history, which says an archived chat should be deletable after it has been archived.

Steps to reproduce

  1. Open Codex / ChatGPT desktop app.
  2. Archive one or more Codex chats.
  3. Open Archived chats.
  4. Inspect an archived chat row and hover over it.

Actual behavior

The only available action is “Unarchive”. No delete/trash option appears, so there is no way to permanently delete the archived chat from this screen.

Expected behavior

Archived chats should expose a delete/trash action as documented, or another clearly discoverable way to permanently delete them.

Additional context

The affected UI shows a list of archived chats with an “Unarchive” button on the right side of every row, but no delete control.

A screenshot of the affected UI is available if maintainers need it.

Reference: OpenAI Help Center, “How to archive and delete Codex chats in the ChatGPT app.”

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Codex desktop app's Archived chats page and trace how each archived chat row exposes the “Unarchive” action. Reproduce the missing delete control with an archived chat, then verify that the row offers a clearly discoverable permanent-delete action and that the behavior matches the referenced Help Center guidance.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.