openai / openai/codex

Return direct Delete action to Codex chat/thread main menu

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

Nobody has claimed this yet.

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

Description

Summary

Please return a direct Delete action to the main chat/thread menu in the new ChatGPT desktop app for Codex chats/tasks, instead of requiring Archive -> Settings -> Archived chats -> Delete.

Current behavior

Codex chat deletion appears to require first archiving the chat, then going to Settings -> Archived chats and deleting from there.

In the observed UI, Settings includes Archived chats, but there is no normal Data controls section and no obvious direct delete action from the chat/thread row.

OpenAI Help currently documents this flow for Codex chats: archive first, then delete from Archived chats.

Expected behavior

Each Codex chat/thread row should expose Delete directly in its main menu, ideally alongside actions such as Archive, Rename, and Pin.

If deleting an active thread needs confirmation, show that confirmation in place.

Why this matters

Deletion is a basic cleanup and privacy control. Requiring archive-first turns a simple action into a multi-step detour, makes the control harder to discover, and is inconsistent with the standard ChatGPT chat deletion behavior documented for the sidebar.

Environment
  • Product: New ChatGPT desktop app with Chat/Work/Codex
  • Area: Codex chat/thread history and Settings -> Archived chats
  • Platform observed: macOS desktop app
  • Date observed: 2026-08-19
Proposed fix

Add Delete back to the chat/thread row main menu:

  • Main menu -> Delete
  • Confirmation dialog: "Delete this chat? This cannot be undone."
  • On confirm, remove it from active/sidebar history and schedule permanent deletion according to the existing retention policy.

Keep Archived chats deletion as an additional management path, but not the only path.

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

The issue names no repository files, tests, or entry points; it concerns the ChatGPT desktop app’s Codex chat/thread history. Start by confirming whether that UI is implemented in this repository, then trace the main thread-row menu and existing Archived chats deletion flow; done means direct Delete with confirmation and active-history removal.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.