[teamleaderleo]

Summary

The ask (from the capture lane, reported by chief-ui and projects-50): "(a) the capture tool's window snapshot leaves out child panels and popovers (NSPanel/child windows), so no popover PR can attach a capture" and "(b) the fleet window snapshot timed out and was refused." Done when "a capture of an open popover shows the popover."

Three causes, three fixes, all in the DEBUG capture path (debug.window_snapshot, which pr-capture's driver.py uses for every still):

• The popover never opened in a capture slot. Slots run the app in the background (CMUX_NEXT_NO_ACTIVATE=1), so there is no key window. home.toggleChiefSettings then picked the front visible window, and AppKit lists a child window before its parent when the app is not active. The front window was Chromium's page window (a CefNSWindow child of the main window), no Home answered, and nothing opened. HomeChiefSettingsPopover.toggleTarget now walks a child window up to its parent, as it already did for a key child panel.
• A glass popover came out as a flat grey card. The snapshot composited the window, then the overlay panels on their own, then menus. A glass or vibrancy panel composited alone has nothing behind it to blur. The window, its child windows and the app's windows over it (menus, cards, popovers that aren't its children) are now one window-server composite (NSWindow.compositedSnapshotWithOverlays()), so the glass blurs the window under it, as on screen. Where a Chromium page image is then painted over the composite, the overlays are cut from that same composite by their own coverage (overlays(cutFrom:includeChild:)) and painted back on top, so a popover over a web page stays on top too. As before, only this app's windows are composited, never another app's.
• The snapshot timed out on a loaded capture mini. debug.window_snapshot ran under the 2 s control-plane deadline, and that deadline counts the wait for the main actor. The capture itself takes about 50 ms, but on cua-5 (load 30 to 44 on 14 cores, shared with builds and test suites) and during app launch, the wait passed 2 s. The driver then had no still, and pr-capture refused the capture. The deadline exists to catch a handler that hangs, but a snapshot queued behind main-actor work isn't hung, and the driver needs the still either way. So the method keeps its own 30 s deadline (DebugWindowSnapshot.controlMethod), which matches the driver's 30 s socket timeout. The route moves out of AppControl into DebugWindowSnapshot so a test can drive it through a real ControlRouter.

cmux window|pane|tab screenshot (AppWindowImage, WindowImageLayer) is left as on base. Two open PRs (#23972, #23983) rework that path, and this one doesn't touch it.

Testing

Red first (471c8b8), then the fix:

• DebugWindowSnapshotDeadlineTests.aSnapshotWaitsBehindABusyMainActor: a router with a 50 ms request deadline, the main actor busy for 400 ms. On base the call fails with a timeout. On the head it answers (no such window for a made-up window number).
• HomeChiefSettingsToggleTests.withoutAKeyWindowAChildInFrontStandsForItsWindow: with no key window and a visible child listed first, the toggle reaches the parent. On base it returned the child.
• WindowSnapshotOverlaysTests.theWindowAndItsOverlaysAreOneCompositeTopmostFirst: the composite's window order (on-screen order first, then unlisted windows, each once).
• WindowSnapshotOverlaysTests.aPopoverCutFromTheCompositeShowsOverAPageImage: pixel check. Where the popover covers the window, the cut shows the popover over a page image; elsewhere the page shows.

cmux-ci compile-check --app passed at the head d04352f (job 29e40325ba693a068a630a72).

Observed / Not run

• Observed: a fleet build of this branch on capture slot cua-5 (load 22 to 40 on 14 cores while it ran). home.show then home.toggleChiefSettings from the CLI, with the app in the background. The window list showed the NativePopupPanel child, and debug.window_snapshot returned in 18 to 51 ms with child_windows: 5. The still shows the Chief Settings popover open with its glass over Home, in light and dark. Before the toggle fix, the same steps opened nothing. Before the composite change, the popover came out as an opaque grey card.
• Observed: the pr-capture run in Proof below (fleet build, capture slot, OCR privacy check).
• Not run: a popover over a Chromium page (the cut path) live; the pixel test covers that compositing.

Changelog

none

Proof

Capture steps-108f6bc705 at d04352ff7e7f (fleet build, capture mini, text checked for private data)

Light	Dark

Steps: cmux action run home.show, then cmux action run home.toggleChiefSettings, with the app in the background as every capture slot runs it. Capture job (fleet build) bdb92487ed96664bf8987012.

Checklist

• Behavior changes have added or updated tests
• Reviewed with an independent reviewer before merge, and all bot and human review comments resolved

Agent session: cosmic-gray

🤖 Generated with Claude Code

[github-actions]

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

Review 53416d1: 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=pr24240 -f ref=leo/capture-child-windows -f platform=macos -f backend_mode=local

web and size checks: green

[teamleaderleo]

Owned by deputy-2 on cosmic-gray · session

[blacksmith-sh]

Found 9 test failures on Blacksmith runners:

Failures

Test	View Logs
/tmp/tmpojodkr0j/summary-missing.json (live):/summary-missing.json (live):	View Logs
/tmp/tmpx3588jkv/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
bench OTHER_SWIFT_FLAGS is 'OTHER_SWIFT_FLAGS=$(inherited) -DCMUX_BENCH_HOOKS -DCMUX_BL OCKING_CHECKS'/ bench OTHER_SWIFT_FLAGS is 'OTHER_SWIFT_FLAGS=$(inherited) -DCMUX_BENCH_HOOKS -DCMUX_BL OCKING_CHECKS'	View Logs
bench OTHER_SWIFT_FLAGS is 'OTHER_SWIFT_FLAGS=$(inherited) -DCMUX_BENCH_HOOKS -DCMUX_BL OCKING_CHECKS'/ bench OTHER_SWIFT_FLAGS is 'OTHER_SWIFT_FLAGS=$(inherited) -DCMUX_BENCH_HOOKS -DCMUX_BL OCKING_CHECKS'	View Logs
test_the_repository_highlights_validate (main.DigestTests.test_the_repository_highl ights_validate)/ test_the_repository_highlights_validate (main.DigestTests.test_the_repository_highl ights_validate)	View Logs

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

[teamleaderleo]

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

[teamleaderleo]

Orphaned: no activity for 13 h, and no lane holds a lease on it. Adopted by the orphan sweep: merged feat-cmux-next in at 20141b1. A later pass queues it for the merge hub if it is reviewed, small and red only on base reds.

[teamleaderleo]

cmux-next crash-class rules / cmux-next crash-class rules is red on 12 of 12 fresh feat-cmux-next PR heads in the last 2:00:00, so it is most likely a base red, not this PR's. The base-reds lane has it; a base merge picks up the fix once it lands.

[teamleaderleo]

cmux-next guards / nightly-guards / workflow-guard-tests / release-notary is red on 18 of 21 fresh feat-cmux-next PR heads in the last 2:00:00, so it is most likely a base red, not this PR's. The base-reds lane has it; a base merge picks up the fix once it lands.

[teamleaderleo]

cmux-next fast gates / post cmux-next/fast-gates is red on 20 of 22 fresh feat-cmux-next PR heads in the last 2:00:00, so it is most likely a base red, not this PR's. The base-reds lane has it; a base merge picks up the fix once it lands.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4029396825001 (5392ef3326)
• cmux NEXT nightly 1.0.0-nightly.4030749448501 (b781e3b4a0)