[teamleaderleo]

Group by Status for the Projects list, behind Labs (Help > Labs…, off by default). Chrome-style groups stay the default. Turn on Group Sidebar by Status in Settings > Labs, then pick Group Projects By > Status (or run "Group by Status").

Stacked on #20452 (the Labs registry); it merges after that one.

What changes

• Sections. Every computer's rows sit under Needs you, Working, Done and No agent, with a count on each header. Chrome groups dissolve in this mode only; the pinned area stays as it is.
• Live moves. Rows move between sections as their status changes. The status is the row's merged one (acpmux turn state, hooks, OSC 7501, cmux status set), so it works the same for Claude, Codex and every ACP harness.
• Stable order. Inside a section, rows keep their list order. The row you're on keeps its section while it stays active; it moves once you switch to another row, so nothing jumps under you.
• Folding. Working, Done and No agent fold and keep their counts; Needs you never folds.
• Row marks (status mode only). A status glyph on every row, a trailing ⚠ on Needs you rows (attention color, danger when it errored), and a laptop, cloud or remote glyph for where the session runs. Colors are Palette tokens, so they follow dark themes and stay apart from group colors. Rows in other modes draw exactly as before.
• Elbow children (second Labs flag, Nest Child Agent Sessions). A child agent session's row hangs off its parent row with the CLI connector ⎿, not an indent, inside the parent's section; its own status still shows on it. The link comes from each chat's acpmux session and its mux.parent tag. Sessions from an older acpmux, or a peer's sessions, get no elbow.
• No bold anywhere in the sidebar.

The two flags are read in one place (SidebarSectionsSetting.parse): with Group Sidebar by Status off, a saved status reads as no grouping, and the elbow needs both flags.

Design panel note: the judges' panel voted Chrome default 4-0 and status grouping as Labs 4-0, and dropped the elbow 0/4. The elbow is Leo's own ask, so it ships as its own Labs sub-option, off by default. Modeled on the session list in Claude Code desktop's 10-14 release (reference captures are in the private screenshots repo only).

Evidence

Each piece's behavior test failed before its fix and passed after, on the fleet (run-swift-testing-suites.sh):

Tests	Red	Green
SidebarStatusGroupingTests (sections, counts, live move, held active row)	e6c50f3	5214f11
SidebarStatusGroupingLabsTests, SidebarGroupByStatusActionTests (flags, Settings choice, action)	a69afbf	a6c674f
status marks test in SidebarStatusGroupingTests	7950ca2	ee33486
SidebarStatusElbowTests, SidebarAgentParentTests	5421acc	c0fe7e9

On the head (33a4247) every suite passed. The step was marked failed only by the fleet's same-tree skip guard on two daemon suites this PR doesn't touch (AcpmuxBundleReplacedTests, AcpmuxOtherHomeDaemonTests).

Not yet established:

• SidebarInsertWhileDisplayAsleepTests failed on two macOS 26 display hosts at earlier heads of this branch; it skips on headless hosts. This PR doesn't touch row-removal motion, and a base run on a display host is in progress to tell whether it fails on base too. I'll update here.
• Light and dark stills and a clip are pending: capture-slot DEV builds currently die on the Debug watchdog (op-next-continuity is fixing it). They'll be added to this body before merge.

Pre-push checks pass on the head: crash ratchet, concurrency, god files (no type or file grew past its limit), system blue, generated settings sources.

Changelog

• Added: Group by Status for the sidebar's Projects list (Labs), with optional nesting of child agent sessions.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Group the sidebar's Projects list by agent status behind labs.sidebarStatusGrouping (Labs, off by default; Chrome-style folder groups remain the default). Rows sit under Needs you, Working, Done and No agent headers with counts, stay in list order inside each section, and move between sections as their merged status changes; the active row keeps its section until another row is selected. Needs you never folds. Rows in this mode gain a status glyph, a trailing warning on needs-you rows, and a glyph for where the session runs.

Labs behavior

• Without labs.sidebarStatusGrouping, a saved sidebar.groupBy: "status" reads as no grouping, and the Group by Status action points to the Labs toggle.
• A second Labs flag, labs.sidebarStatusElbow (Nest Child Agent Sessions, off by default), hangs a child agent session's row off its parent row with the ⎿ connector, in the parent's section; parent links come from each chat's acpmux session and its mux.parent tag.

^{Written for commit 2984b44. Summary will update on new commits.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: manaflow-ai/cmux/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 3a4a1594-9de2-4b18-9c3d-99d7d357f7fa

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[blacksmith-sh]

Found 7 test failures on Blacksmith runners:

Failures

Test	View Logs
GitHub-hosted runner label: .github/workflows/ intent-familiar-review.yml:21: runs-on: ubuntu-24.04	View Logs
GitHub-hosted runner label: .github/workflows/ pr-red-checks-comment.yml:16: runs-on: ubuntu-24.04	View Logs
test/chat-find.test.ts/chat-find.test	View Logs
test/chat-find.test.ts/chat-find.test	View Logs
test_scans_only_test_sources (main.CommandLine.test_scans_only_test_sources)/ test_scans_only_test_sources (main.CommandLine.test_scans_only_test_sources)	View Logs
test_scans_the_ui_test_sources (main.CommandLine.test_scans_the_ui_test_sources) (p ath='ios/cmuxUITests/ProbeTests.swift')	View Logs
two failed fetches then a success did not pass/ two failed fetches then a success did not pass	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[github-actions]

Probably yours: Fast static checks failed: a static check failed, FAILED localization (0.93s).

CI failed on 2984b44504 (run 38683857018 attempt 1): 2 code, 7 unknown.
macOS jobs did not run: compile and app tests were skipped: Fast static checks failure.

Job	Verdict	Why
Fast static checks	code	a static check failed
CI fast guards	unknown	no known signature; failed step: Run the fast guard tests
guards / workflow-guard-history	unknown	no known signature; failed step: Validate SwiftPM lockfile policy
guards / workflow-guard-tests / release-ios	unknown	no known signature; failed step: Validate iOS simulator build-once contract
guards / workflow-guard-tests / app-host-cache	unknown	no known signature; failed step: Validate iOS video recording failures
guards / workflow-guard-tests / preflight	unknown	no known signature; failed step: Validate macOS runner guards
guards / workflow-guard-tests / quality-determinism	code	a Python test failed
guards / workflow-guard-tests / release-tooling	unknown	no known signature; failed step: Validate retried Ghostty Zig package fetches
web / react-apps-check	unknown	no known signature; failed step: Test webviews

Matched log lines

Fast static checks: FAILED localization (0.93s)
guards / workflow-guard-tests / quality-determinism: FAIL: test_scans_only_test_sources (__main__.CommandLine.test_scans_only_test_sources)

Not re-run automatically: Fast static checks, CI fast guards, guards / workflow-guard-history, guards / workflow-guard-tests / release-ios, guards / workflow-guard-tests / app-host-cache are not machine failures.

Written by scripts/ci/classify_failures.py (ci-failure-attribution.yml); signatures are its SIGNATURES table. A machine verdict is the runner's fault, not this PR's; yours means the failing file is one this PR changes, also red on main that main's latest full suite fails the same way, seen on other PRs that it failed on another pull request's run lately.

[github-actions]

CI fast guards failed on 2984b44504 (https://github.com/manaflow-ai/cmux/actions/runs/38683857018). It does not block the merge; a red guard merged into main breaks it for every open PR.
The log named no failed step; see the run.

Agents: python3 scripts/ci/guard_attribution.py fix applies the mechanical fixes locally. This comment is updated in place on each push.

[teamleaderleo]

Superseded by #20905: same Group by Status work, moved off the Labs registry onto Debug settings toggles (Lawrence via Leo, 10-15: no Labs; opt-in looks are Debug toggles, off by default). #20452 is no longer a dependency.