[teamleaderleo]

Adds a DEV-only control method, debug.chief_workspaces, so a capture slot can show the Chief's sidebar group from #23391 and #23546. In a slot the app starts the Chief owner, but nothing starts subagents there, so the group is empty and draws nothing.

• Same path as a person's New Workspace. It opens named workspaces on the local Chief machine through services.windows.createWorkspace(_:on:into:), the call behind the sidebar machine's New Workspace. It waits up to 30 s for the Chief owner to connect.
• Params: open: [name] opens the named workspaces; command sets what each one runs, so a still can avoid showing the mini's shell prompt; collapse: Bool folds or opens the Chief group through the sidebar's own .toggleCollapse intent; card: Int shows the hover card of one opened workspace.
• Compiled out of release builds, not just hidden at runtime. Server/ChiefCaptureControl.swift is wrapped in #if DEBUG as a whole, and its one registration sits inside AppControl's existing #if DEBUG block. tests/test_cmux_next_debug_only_controls.py pins both.
• No new socket permissions. It is one more debug.* method on the existing router.
• New tour: scripts/cmux-next/media/tours/chief-group.json.

The Chief group, expanded, from a capture slot through this method (open, command: cat, cwd: /tmp):

Capture steps-1d7dabed80 at 1c393a7ed552 (fleet build, capture mini, text checked for private data)

Light	Dark

The folded group and both themes were captured too (local only); folding moves the list about 52 pt down, which is a separate fix. The right-click menu's "Started by Chief" item cannot be captured: debug.window_snapshot takes only the main window, and an NSMenu is a separate window. I have not worked around that.

Agent session: cosmic-gray

🤖 Generated with Claude Code

---

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

---

Summary by cubic

Adds debug.chief_workspaces, a DEBUG-only control that lets a capture slot show the Chief's sidebar group, which is otherwise empty because nothing starts subagents there.

The control opens named workspaces through the same createWorkspace path as the sidebar's New Workspace, waits on an observation for the Chief owner (up to a 60 s deadline), and can fold the group or show a row's hover card. A command and cwd param keep the mini's shell prompt and home path out of stills. The control and its registration sit inside #if DEBUG, so release builds compile them out; tests/test_cmux_next_debug_only_controls.py pins both and now runs in CI. Adds a tour at scripts/cmux-next/media/tours/chief-group.json.

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

[github-actions]

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review e2f1d90: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr23638 -f ref=chief-sidebar-2/chief-capture -f platform=macos -f backend_mode=local

Not verified: macOS jobs did not run: compile and app tests were skipped on e2f1d9060d; ci-status is green without them.

CI passes on e2f1d9060d (run 39661397982 attempt 1).
macOS jobs did not run: compile and app tests were skipped: Fast static checks skipped (the macos job needs both to succeed). Re-run CI once they pass, before merging.

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.

red: cmux-next checks (god files, concurrency, crash safety, l10n); no finished base run on e07aaec to compare; do not merge until green; see lane-rules

[teamleaderleo]

Owned by chief-sidebar-2 on cosmic-gray · session

[blacksmith-sh]

Found 9 test failures on Blacksmith runners:

Failures

Test	View Logs
/tmp/tmp4b1pqo16/summary-missing.json (live):/summary-missing.json (live):	View Logs
/tmp/tmppduzzhbj/summary-fail.json (live):/summary-fail.json (live):	View Logs
[new_workspaces] debug.new_workspace timed 0 of 50 new workspace rows/ [new_workspaces] debug.new_workspace timed 0 of 50 new workspace rows	View Logs
[new_workspaces] the window draws no frames/[new_workspaces] the window draws no frames	View Logs
[tabs] debug.tab_switch timed 0 of 40 switches/ [tabs] debug.tab_switch timed 0 of 40 switches	View Logs
[tabs] the window draws no frames/[tabs] the window draws no frames	View Logs
convention violations found (ERROR lines above)./ convention violations found (ERROR lines above).	View Logs
test_a_file_a_test_reads_selects_that_test (main.PullRequestTiers.test_a_file_a_tes t_reads_selects_that_test)/ test_a_file_a_test_reads_selects_that_test (main.PullRequestTiers.test_a_file_a_tes t_reads_selects_that_test)	View Logs
test_a_shared_module_selects_its_dependents (main.PullRequestTiers.test_a_shared_mo dule_selects_its_dependents)/ test_a_shared_module_selects_its_dependents (main.PullRequestTiers.test_a_shared_mo dule_selects_its_dependents)	View Logs

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

[teamleaderleo]

Bead cx-bdgvo created for this PR by the cmux coordinator.

[teamleaderleo]

Review (subagent, correctness first): SHIP at e2f1d90. Remaining reds are base reds: cmux-next checks fails only on Tier routing (and the ChiefWorkspaceName namespace lint, fixed by #23678), and crash-class rules flags HomeSidebarSplitView+Drop.swift:11, a base file. Fast gates pass; the app compiles on the fleet.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.3967575499801 (2a0a42ab31)
• cmux NEXT nightly 1.0.0-nightly.3967669311101 (2a3491e235)
• cmux NEXT nightly 1.0.0-nightly.3967869181901 (cd9b30e302)
• cmux NEXT nightly 1.0.0-nightly.3968001295301 (8cba1da27d)