codex - 💡(How to fix) Fix Codex Web UX Issues: No Chat Organization, No Rename, and Archived Chats Not Accessible [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17182Fetched 2026-04-09 08:01:32
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2closed ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

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.

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

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

extent analysis

TL;DR

Implementing project/folder-based chat organization, chat renaming, and an "Archived Chats" section with restore option can improve usability and reduce errors in Codex.

Guidance

  • Consider organizing chats into separate folders or projects to manually manage conversations and reduce context mixing.
  • Use descriptive text in chat descriptions to temporarily work around the lack of renaming functionality.
  • Request or wait for the implementation of an "Archived Chats" section to access and restore archived conversations.
  • Explore existing features or extensions for tagging or labeling conversations as a potential workaround.

Example

No code snippet is applicable in this scenario as the issue is related to feature requests and usability improvements.

Notes

The provided suggestions are based on the assumption that the user has explored existing features and settings within Codex. The implementation of the suggested improvements may require updates or changes from the OpenAI team.

Recommendation

Apply workaround: Implement manual chat organization and description practices to mitigate current usability issues until the suggested features are implemented.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING