Codex review sub-sessions are shown as standalone sessions in the UI

[akolotov]

Problem

CodeDash currently shows Codex review sub-sessions as separate top-level sessions in the UI, even though they are part of the main session workflow.

A concrete example is when a main Codex session triggers code review and a separate review session is created. Both sessions are then displayed independently in Grid/List view, which makes the session list noisier and can mislead the user into treating the review session as unrelated work.

Observation

Codex session metadata already appears to expose a usable signal for this:

"source": { "subagent": "review" }

This should allow the UI to identify at least review sub-sessions explicitly.

Suggested improvements

Either of these would improve the UX:

1. Add a toggle to include/exclude Codex sub-agent sessions.

   • Default: disabled, so sub-agent sessions are hidden unless the user opts in.

2. Mark Codex sub-agent sessions explicitly in Grid/List view.

   • For example with a badge or secondary label such as Sub-agent, Review, or similar.

Why this matters

Without this distinction, the UI presents implementation-detail sessions as if they were peer sessions. That increases clutter and makes it harder to understand the actual primary conversation flow.

Implementation hint

Use session metadata such as:

"source": { "subagent": "review" }

to detect Codex sub-agent sessions and adjust the UI behavior accordingly.

[vakovalskii]

Привет, принял разберем

[vakovalskii]

PR #59 merged (Codex message count fix). Sub-session filtering is a separate feature — reopen if needed.

[akolotov]

PR #59 merged (Codex message count fix). Sub-session filtering is a separate feature — reopen if needed.

#59 and #38 are not related to each other, aren't they?