Codex App: add flags, labels, icons, or folders for organizing chats

Open 💬 3 comments Opened Jun 14, 2026 by joshka
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Variant: App

What feature would you like to see?

It would be useful to organize chats with something more flexible than pinning.

When working across several tasks at once, pinning is too coarse: everything important ends up in one bucket. A lightweight marker would make it easier to come back to chats by purpose, such as bugs, feature work, follow-up items, reviews, or blocked tasks.

This could take a few forms, and different users organize work differently:

  • flags, colors, or icons for quick visual markers
  • labels/tags for searchable categories
  • folders or grouped views for people who prefer filing things explicitly

I do not have a strong opinion that one of these has to be the only model. Even supporting a simple version of one or two modes would help, as long as users can choose the organization style that fits how they work.

Additional information

The mental model is similar to email clients: some people search, some people file, some people label, and many use a mix. Codex chats have the same problem once there are enough parallel tasks.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

  • #26762

Powered by Codex Action

bc1224 · 7 days ago

This is so needed, my chats get lost very easily without this.

mkostrus-gif · 23 hours ago

Please support nested folders inside each Codex project, not only a single flat grouping level. Users should be able to create subfolders, move chats/tasks into them (ideally with drag-and-drop), and collapse or expand each level.

Example:

Project
├─ CAD
│  ├─ Plugins
│  └─ Blocks
├─ Documents
└─ Archive

Once a project contains many chats, the current flat list is difficult to scan visually and it becomes unnecessarily hard to find an older task. The folder hierarchy should be organizational metadata only and should not change a task's working directory or local files.