You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codex Web UX Issues: No Chat Organization, No Rename, and Archived Chats Not Accessible #17182
I'm using Codex heavily for development across multiple projects, and I'm facing major usability issues with chat management in Codex Web.
Problems:
No project/folder-based organization
All chats are in a flat list. When working on multiple projects, it's very easy to accidentally send messages to the wrong chat, causing incorrect context usage and wrong outputs.
No option to rename chats
There is no clear way to rename chats, making it difficult to identify and manage conversations.
Archived chats are not visible
When chats are archived, they seem to disappear completely, almost like they are deleted. There is no clear way to view or restore archived chats.
Impact:
High risk of mixing project contexts
Incorrect code generation due to wrong context
Loss of important conversations (archived chats)
Reduced productivity
Suggested Improvements:
Add project/folder-based chat organization
Allow renaming chats
Provide a clear "Archived Chats" section with restore option
Optional: tagging or labeling system
These improvements would significantly enhance developer workflows and reduce errors.
Thanks for the feedback. Most of this is already captured in other feature requests. Please upvote those. If there is something that's not captured in an existing feature request, please open new feature requests — one idea per issue.
Activity
github-actions commentedon Apr 9, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Apr 9, 2026
Thanks for the feedback. Most of this is already captured in other feature requests. Please upvote those. If there is something that's not captured in an existing feature request, please open new feature requests — one idea per issue.