Codex app: add delete chat/message and move selected messages between projects
What variant of Codex are you using?
App
What feature would you like to see?
Feature request
Please add better chat/message management tools to the Codex app so project context can be kept clean.
Problem
Users can accidentally enter unrelated messages into the wrong project chat. This pollutes the project context and can make future Codex responses less accurate.
Users may also create duplicate chats accidentally. Currently, chats can be archived, but there is no obvious permanent delete workflow, and no way to move selected messages into the correct project/chat.
Requested improvements
- Add Delete chat to the sidebar/right-click context menu, separate from Archive chat.
- Add a confirmation dialog before permanent deletion.
- Allow bulk select/delete/archive for duplicate chats.
- Allow deletion of individual unwanted messages inside a retained chat, where technically possible.
- Allow selected message(s) to be moved from one project/chat to another.
- Clarify whether
Edit -> Deleteapplies to selected text, selected messages, or sidebar chat items. - Rename or clarify Archive chat behavior so users know whether it is reversible.
Why this matters
Project chats become long-running working records. A single unrelated message or accidental duplicate chat can pollute context, confuse later work, and make it harder to maintain an accurate project history.
Related
This is related to project/chat organization requests such as:
https://github.com/openai/codex/issues/13836
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
We built a small open-source macOS tool for managing local Codex App/CLI conversation history:
https://github.com/LeeeeTX/codex-history-cleaner
It provides a terminal UI to list, search, preview, and delete local Codex sessions from
~/.codex. Deletion is recoverable by default with backups, and permanent deletion is also available with an extra confirmation step.Hope this is useful for anyone who wants local controls for Codex history cleanup.
I would argue that this Feature Request is not fulfilled by the other requests, and therefore should NOT be marked as Duplicate.
In particular, these two (2) specific funtions do not appear to be represented in any of the other tickets for which one was marked Duplicate:
I would request that this request be re-opened on that basis.