codex - 💡(How to fix) Fix Add groups [1 comments, 2 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#19248Fetched 2026-04-24 05:58:03
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3closed ×1commented ×1

Root Cause

Why? because the project space is littered with many threads of the same issue. why? because sometimes i have one ai create the plan, in a thread, and another review it (lots of misses are catched that way). But now i have multiple (sometimes up to 3) threads relating to the same topic. And they are scattered and hard to differentiate because they are not in order. Why? because once an ai finishes a thread it bubbles up to the top, so order isnt maintained.

RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

App

What feature would you like to see?

On the projects section unders a project folder, we have many threads. It would be nice that a thread itself can be a group just like the folder (not for all of them, but for those we want).

Why? because the project space is littered with many threads of the same issue. why? because sometimes i have one ai create the plan, in a thread, and another review it (lots of misses are catched that way). But now i have multiple (sometimes up to 3) threads relating to the same topic. And they are scattered and hard to differentiate because they are not in order. Why? because once an ai finishes a thread it bubbles up to the top, so order isnt maintained.

groups stop this. It should be optional for that stubborn topic that needs 2-3 ai looking at it.

Additional information

No response

extent analysis

TL;DR

Organizing threads into groups within a project folder could help mitigate the issue of scattered and hard-to-differentiate threads.

Guidance

  • Consider implementing a feature to allow threads to be grouped, similar to how folders are currently used, to improve organization and reduce clutter in the projects section.
  • This could involve adding a "group" or "category" option to threads, allowing users to selectively group related threads together.
  • To address the issue of threads bubbling up to the top after an AI finishes, consider implementing a sorting or filtering system that allows users to maintain a custom order or prioritize certain threads.
  • Investigate how to make this grouping feature optional, so it can be applied only to specific threads or topics that require multiple AI reviews.

Notes

The exact technical implementation details are unclear, and more information would be needed to provide a specific solution. However, the general idea of introducing a grouping feature for threads could help address the user's concerns.

Recommendation

Apply workaround: Implement a custom sorting or filtering system to help users maintain order and prioritize threads, while exploring the possibility of introducing a grouping feature in the future.

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

codex - 💡(How to fix) Fix Add groups [1 comments, 2 participants]