[Feature]: Prioritize Sidebar V2 threads that need review #4695

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

Sidebar V2 currently keeps active threads in creation order even when their status changes. A thread that has just finished can remain below several agents that are still working, so the next item that needs a person's attention is easy to miss.

This affects both the desktop/web sidebar and the native mobile thread list.

Proposed solution

Add an opt-in automatic ordering mode to the existing Sidebar/Thread List V2 settings:

1. Group active threads by attention state.
2. Default the priority to Needs review → Working → Other active.
3. Let the user reorder those three groups.
4. Within Needs review, show the most recently completed or attention-worthy thread first.
5. Clear a completed thread's device-local review priority when the user opens it.

Keep current creation-order behavior as the default, and leave Snoozed and Settled behavior unchanged.

Why this matters

The sidebar becomes an attention queue: finished, blocked, failed, or input-waiting work appears before work that is still progressing. Users can review completed work promptly without losing the ability to choose a different group priority.

Smallest useful scope

One device-local preference for automatic ordering and one preference for the three-group priority, shared by the web/desktop Sidebar V2 and native mobile Thread List V2 implementations. No server protocol or database migration.

Alternatives considered

• Hard-code Needs review first. This solves the immediate case but gives users no control over differing workflows.
• Always sort by last update. This causes working threads to churn and does not distinguish items that need human attention.
• Change the default globally. Keeping the feature opt-in avoids surprising existing Sidebar V2 users.

Risks or tradeoffs

The implementation touches both web and mobile because both clients expose Sidebar V2 independently, so the contribution is larger than a single-surface UI tweak. The behavior is nevertheless one setting contract and one ordering model. I would appreciate maintainer guidance on whether that cohesive cross-platform scope is acceptable in one PR or should be split by client.

Contribution

• I would be open to helping implement this.