Codex Web UX Issues: No Chat Organization, No Rename, and Archived Chats Not Accessible

Resolved 💬 2 comments Opened Apr 9, 2026 by patel28 Closed Apr 9, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

Vscode Extension In Ubuntu

What feature would you like to see?

Hi OpenAI Team,

I'm using Codex heavily for development across multiple projects, and I'm facing major usability issues with chat management in Codex Web.

Problems:

  1. 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.

  1. No option to rename chats

There is no clear way to rename chats, making it difficult to identify and manage conversations.

  1. 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!

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #16818
  • #16147
  • #16697
  • #16673
  • #16089

Powered by Codex Action

etraut-openai contributor · 4 months ago

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.