Windows: deleting archived Codex chats fails despite enabled delete button
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Codex Desktop / Windows package version: 26.901.6511.0 (verified from the installed OpenAI.Codex package on 2026-09-06).
What platform are you using?
Microsoft Windows 11, x64.
What issue are you seeing?
The Settings > Archived chats page shows the trash-can delete button and the “Delete all” button, but deleting an archived Codex chat fails. The UI displays the error:
无法删除已归档聊天
(English equivalent: “Failed to delete archived chat”.)
The archived chat remains visible after the failed operation.
Steps to reproduce
- Archive a Codex chat from the desktop app.
- Open Settings > Archived chats.
- Click the trash-can icon beside an archived chat.
- Confirm deletion if prompted.
- Observe the “无法删除已归档聊天” error and that the chat remains.
Expected behavior
After confirmation, the archived chat should be removed from the archived-chat list and permanently deleted according to the documented Codex chat-deletion behavior. If deletion is unsupported for a host or chat type, the UI should explain that clearly instead of presenting an enabled delete button.
Additional information
The official Help Center documents deletion from Settings > Archived chats, so this is not an intentional “archive-only” limitation:
https://help.openai.com/en/articles/20001333-how-to-archive-and-delete-codex-chats-in-the-chatgpt-app
A similar report exists as openai/codex#28095 (“Archived chats show a Delete button, but deletion does not work”), although that report used an older macOS build.
Local desktop logs show the app issued a thread/delete request for an archived conversation, but the UI still reported failure. No account identifiers, conversation contents, or local paths are included here.
Please investigate the Windows archived-chat deletion path, including host capability detection and the handling of the thread/delete response/error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Windows Settings > Archived chats delete action and the logged thread/delete request, then inspect host capability detection and response/error handling. Done means an archived chat is removed after confirmed deletion, or the UI clearly explains when deletion is unsupported; compare behavior with the related archived-chat report if useful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100