Codex App: first-class multi-label tagging for sessions in the GUI

Open 💬 1 comment Opened Jul 29, 2026 by 674019130
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

App / Codex Desktop

What feature would you like to see?

Please add first-class user-defined tags for sessions/threads in the Codex App GUI. This is a focused request for tagging, not only folders, pinning, manual ordering, or renaming.

The core workflow should support:

  • Create reusable text tags with optional colors.
  • Assign one or more tags to a session from its context menu.
  • Display compact tag chips or color markers in the sidebar.
  • Filter/search sessions by one or multiple tags.
  • Rename, recolor, remove, and clear tags.
  • Keep tags independent from generated session titles, projects/workspaces, and Git metadata.
  • Persist tag assignments across app restarts and resume flows, with predictable behavior for forks.

Typical tags include both workflow state and topic, for example:

  • in progress, blocked, waiting, follow up, done
  • frontend, backend, release, research, review

Pinning creates only one flat bucket, while renaming destroys or obscures the useful generated title. Folders also force a session into a hierarchy, whereas multiple tags can describe both status and topic. Once the sidebar contains many sessions, this becomes a practical navigation need rather than cosmetic metadata.

Related requests and duplicate-chain assessment

I reviewed the current related issues before posting. GitHub Actions has produced a chain of potential-duplicate comments, but most links are similarity suggestions rather than maintainer-confirmed duplicates:

| Issue | Scope | Assessment |
| --- | --- | --- |
| #28213 | Flags, labels, icons, or folders | Broad umbrella request; includes labels but does not define a concrete tag workflow. |
| #29978 | Independent labels for threads and projects | Closest existing request and strong protocol/storage proposal; this issue emphasizes the end-user GUI and multiple-tag workflow. |
| #30451 | Custom groups and color status markers | Overlaps with color/status, but centers on grouping and treats markers as an additional mechanism. |
| #30986 | Project-level topics/grouped threads | Hierarchical grouping rather than tagging. |
| #32124 | Nested session/thread folders | Closed by its author as a duplicate of #30986; folder-specific. |
| #29297 | Saved views, regex filtering, and custom sorting | A complementary consumer of tag metadata, not the tagging model itself. |
| #28692 | Manual ordering and sidebar sections | Ordering/sections rather than tags. |
| #26762 | Pinning and custom sorting | The bot linked this from #28213, but its core request is manual ordering, not labels. |
| #12699 | Organize threads in folders | Folder request closed as not planned after insufficient upvotes. |

The automated chain is roughly:

#32124 → #30986 → #30451 → #29978 → #28213 → #26762

There are also cross-links from #30451 to #29297 and from #29297/#28692 back to #28213. Of these, only #32124 was explicitly closed by a human as a duplicate. The other relevant issues remain open and cover meaningfully different organization models.

This issue intentionally records the focused product requirement: sessions in the GUI need reusable, visible, filterable, multi-value tags. If the team chooses an existing issue as the canonical tracker, please link/merge this requirement there rather than reducing it to folder or sorting support.

Additional information

A minimal first release could support locally persisted text-and-color tags, assignment from the session context menu, sidebar chips, and a single-tag filter. Multi-tag filtering and saved views could follow later.

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 1 month ago

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

  • #35467

Powered by Codex Action