Add custom thread groups and color status markers for better conversation list organization

What variant of Codex are you using?

App 26.623.42026

What feature would you like to see?

Summary

The current Codex App conversation list management feels somewhat limited. It would be very helpful to support custom user-defined groups for conversations, and optionally allow users to add small custom color markers to threads.

Problem

As the number of Codex sessions grows, the conversation list becomes harder to manage. Pinning or relying on recent order is not always enough, especially when different sessions represent different kinds of work.

There are a few common cases where better organization would help:

1. Some sessions are paused halfway through because they cannot be continued immediately.
2. Several sessions may all belong to the same feature or project area.
3. Some sessions are more urgent or higher priority than others, even if they are not the most recent ones.

Right now, it is difficult to express these distinctions in the conversation list.

Proposed solution

Add support for user-defined thread groups in the Codex App conversation list.

For example, users could create groups such as:

• Paused
• Needs review
• Feature: billing flow
• Feature: onboarding
• Follow up later
• Experiments

A thread could be assigned to one custom group, or possibly multiple groups if that fits the product model better.

In addition, it would be useful to allow users to attach a small custom color marker to a conversation. These markers could be used to visually represent status or priority, such as:

• Red: urgent / blocking
• Yellow: needs follow-up
• Green: ready / completed enough
• Blue: related to a specific feature area
• Gray: parked / inactive

The color marker does not need to enforce any workflow by itself. Even a lightweight visual tag would make it much easier to scan the thread list.

Use cases

Paused work

Sometimes a Codex session reaches a point where work cannot continue yet, but the session should not be forgotten. A custom group like "Paused" or "Waiting" would make these sessions easy to find later without keeping everything pinned.

Feature-based organization

When multiple conversations are all related to the same feature, custom grouping would make it easier to keep the work together. For example, one feature might have separate threads for implementation, review, debugging, UI polish, and release notes. Grouping them under the same feature would make the conversation list much more useful.

Priority scanning

Color markers would help users quickly distinguish which conversations need attention first. This would be especially useful when many sessions are active in parallel.

Expected benefits

• Easier management of many Codex sessions
• Better support for parallel feature work
• Less reliance on pinning as the only organization mechanism
• Faster visual scanning of the conversation list
• More flexible personal workflow without requiring a heavy project-management system

Alternatives considered

Pinning helps keep important sessions visible, but it does not communicate why a session is important or how it relates to other sessions.

Search can help find older sessions, but it is less useful for maintaining an active working set.

A full project-management workflow may be too heavy for this need. Lightweight custom groups and color markers would solve the common cases with much less complexity.

Additional context

This request is mainly about improving conversation list organization for users who run many Codex sessions in parallel. The feature could start simple: custom groups plus a small optional color marker per thread would already cover many workflows.

Additional information

_No response_