Tags, Labels, and Statuses for Codex Threads

What variant of Codex are you using?

App and VS CODE

What feature would you like to see?

I’m actively developing Atlaso, a fairly large software project, and I use Codex extensively across many parallel threads for feature development, bug fixing, testing, refactoring, PR work, research, and follow-up tasks.

As the number of Codex threads grows, one limitation becomes increasingly noticeable: there is no effective way to organize and manage threads at scale.

I would like Codex to support tags/labels and thread statuses, with both manual and automated assignment.

The basic idea would be to allow users to create custom tags and assign one or more tags to each thread. For example:

Atlaso + Bug + Working

Atlaso + Feature + Waiting for PR

Atlaso + PR Review + Needs Attention

Atlaso + Done

Tags should be searchable and filterable, and optionally have colors so that the state and purpose of a thread can be understood quickly from the thread list.

In addition to normal tags, it would be very useful to have a concept of thread status, either as a dedicated field or as a special type of tag. Example statuses could include:

New, Working, Waiting, Done, Failed, and Needs Attention.

The most important part for me would be automation support. Codex or an agent should be able to assign or update tags/statuses programmatically as the work progresses.

For example, a thread could automatically transition through:

New → Working → Waiting for PR → Done

or:

New → Working → Failed / Needs Attention

This could also be tied to events such as a PR being created, comments being added, tests failing, a PR being merged, or an agent determining that human input is required.

For a project like Atlaso, the Codex thread list effectively becomes a work queue. Right now, once there are many threads, it becomes difficult to answer simple questions such as:

• Which Atlaso tasks are still being worked on?
• Which threads are waiting for a PR or review?
• Which tasks failed or require my attention?
• Which threads are already completed?
• Which threads belong to a specific area of the project?
• Where was a particular bug or feature discussed?

Being able to filter for something like Atlaso + Needs Attention or Atlaso + Working would make a major difference.

This would make Codex much more practical as a long-running engineering workspace for users managing many concurrent development tasks, rather than having the thread list become an increasingly difficult-to-search collection of conversations.

Additional information

No response

No files, tests, or entry points are named. Start by locating the Codex thread-list implementation and its existing search or filtering behavior, then define how custom tags, statuses, and automated updates should fit across the App and VS Code; done means threads can be tagged, filtered, and transitioned through the requested workflow.