[teamleaderleo]

cmux NEXT gets a host pressure indicator in the window's top row, after the toolbar band and the incognito badge, with a popover. It's part 2 of cmuxterm-hq#2995, on the monitor that #24298 landed. While the host is normal it shows nothing. At warning or critical it shows a still glyph in the theme's attention color, with no pulse or animation. Clicking it opens a popover with the load against its limit, acpmux's other reasons, its turns and processes, its busiest sessions with Stop (it asks first, and the session stays to resume), and Open Agent Activity.

It ships off by default behind Debug toggle hostPressure.enabled (cmux#22662). Release and RC never activate the tunable store, so they keep it off.

coord-deputy's order, quoted:

"the indicator plus popover, with one 15 s timer that stops when the window is hidden and states its cleanup."
"Split HostBudget.swift for the god-file warning."
"It's a new dev surface, so both ship off by default behind a Debug/Labs toggle (cmux#22662)."
"Codex review at the exact head, green compile, before/after numbers for the timer's cost."

Off means inert

With hostPressure.enabled off (the default), the indicator never creates HostPressureService. That means no monitor, no memory pressure source, no 15 s timer and no sysctl or acpmux reads. The only thing it keeps is an Observation of that one tunable key, which is event-driven and costs no wakeups. HostPressureForce (the hostPressure.force Debug Settings choice for captures) does nothing while the toggle is off.

The timer: stop condition and cleanup

There is one 15 s timer (2 s leeway) for the whole app: HostPressureMonitor's DispatchSourceTimer, not one per window. It runs only while at least one window's indicator is subscribed. An indicator is subscribed while HostPressureSampling.samples is true, meaning the toggle is on and its window can be seen: the app isn't hidden, and the window is isVisible, not minimized, and occlusionState.contains(.visible).

• Stop condition: an indicator unsubscribes when the toggle goes off, or when its window hides (app hidden or another Space), minimizes, is fully occluded or closes. It hears about these through didChangeOcclusionState, didMiniaturize, didDeminiaturize, willClose, the app's didHide and didUnhide, and the toggle's Observation. When the last indicator unsubscribes, HostPressureService calls HostPressureMonitor.stop(). App quit calls it too.
• Cleanup: stop() cancels the memory pressure source, the timer and any read in flight, and drops a level change that is still queued. Its window and app notifications (through NotificationCenter.notifications), the toggle Observation and the level Observation are tasks held in HostPressureTasks bags, and each body returns at once if its task was cancelled. A window change, willClose and the nonisolated deinit cancel them on whatever thread they run, and the indicator unsubscribes. Its subscription is a HostPressureSubscription token: if the token is released without cancel() (an indicator freed off the main thread), it unsubscribes on the main actor, so a window never leaves a subscriber that would keep the timer running (aSubscriptionReleasedWithoutCancelStillUnsubscribes).
• plans/cmux-next/idle-wakeups.md has the same row.
• HostPressureIndicatorTests covers the stop condition. theToggleShipsOffAndOffNeverMakesTheService checks that the default is off and that, with the toggle off and the window visible, the indicator never creates a service. itSamplesOnlyWhileOnAndVisible checks that with the toggle on and the window visible the monitor runs, that it stops when the window becomes invisible, that it runs again when the window is visible again, and that it stops when the toggle goes off. theGateIsTheToggleAndTheWindow checks the gate's truth table.

Timer cost (one harness, fleet mini)

scripts/cmux-next/bench_idle.py on fleet mini cmux20-bench (M-series, 12 cores, macOS 27, logged-in console). Each run is one tagged DEV build launched clean, with 30 s settle and then 300 s measured per scenario. The app's CPU and wakeups come from proc_pid_rusage at the start and end of each window. Base is c7e203d361 and head is 9a9b4d7dc8, each with one measurement-only commit (an hp-on scenario that sets hostPressure.enabled through debug.tunables; branches app-eff/hpi-bench-base and app-eff/hpi-bench, not for merge). The later review fixes change when a window subscribes and guard the start, not the timer's interval.

build	scenario	app CPU %	app wakeups/s	app wakeups/min
base	window visible (no indicator code)	0.74	251.8	15,109
base	window minimized	0.66	280.1	16,807
head	toggle off (default), window visible	1.13	251.6	15,098
head	toggle on, window visible	0.65	284.4	17,065
head	toggle on, window minimized	0.12	5.1	304

What this shows: off = no change. Head with the toggle off measures 251.6/s against base's 251.8/s in the same scenario. The timer's expected cost when on is 4 wakeups/min (0.07/s), which is far below this harness's run-to-run noise. Base alone moves 28/s between its two scenarios, and almost all of the app's ~250/s idle wakeups come from outside this code (the WakeupLedger shows CEFMessagePump at about 0.7/s and BusyWatchdog at 0.1/s; the rest isn't attributed). So the on-visible (+33/s) and minimized (-275/s) rows are noise around a large baseline, not this timer. The timer's cost and its stop come from the code and its tests instead: one DispatchSourceTimer at 15 s with 2 s leeway, so 4 fires/min while running. itSamplesOnlyWhileOnAndVisible shows isMonitoring going false (timer cancelled) on hide and on toggle-off, and theToggleShipsOffAndOffNeverMakesTheService shows no service, and so no timer, while off.

Size

About 1,050 changed lines, over the ~800 target. The popover, indicator, service and their tests are one feature behind one toggle, and the parts that could stand alone (the HostBudget.swift split and the 21-locale catalog) already landed as #24506 and #24508.

Split into PRs that each land on their own

• This PR: the indicator, popover, service, Debug toggle, tests and tour, with English text as the String(localized:) default values.
• cmux NEXT: split HostBudget.swift into the formula and the verdict (no behaviour change) #24506 (merged as effb5e4019): HostBudget.swift split in two (6 top-level types, limit 3), with no behaviour change.
• cmux NEXT: host pressure indicator strings in all 21 locales #24508 (merged as 97377b197b): HostPressure.xcstrings in all 21 locales. It comes whole rather than as non-English only, because the localization debt ratchet fails a catalog that has English but lacks the required locales.

The Codex review took six passes. They found and fixed these: app hide wasn't observed; an off-main deinit left observers, tasks or a subscriber running (fixed with HostPressureTasks and HostPressureSubscription); a start hop overtaken by the last leave still started the timer (fixed with HostPressureMonitor.start(while:), which checks on the monitor actor before it builds the timer, so this PR touches the part-1 library by 5 lines); a callback queued before cancellation could still resubscribe; a newly shown indicator didn't get laid out; and a forced level's sample sessions showed a Stop that did nothing (now hidden). The tests await the monitor's own isRunning (aStartOvertakenByTheLastLeaveStartsNothing, aStartNoLongerWantedStartsNothing, windowAndAppNotificationsStartAndStopSampling with occlusion, hide, unhide and close posted to an injected center). This PR also fixes a compiler crash on the branch ("failed to produce diagnostic" at HostPressureService.swift:53). The acpmux reader is now a plain closure instead of Optional.map returning a closure.

Observed / Not run

• Ran: prepush-gate.py (no new violations), cmux-ci compile-check --app and the HostPressureIndicatorTests,HostPressureMonitorTests,HostPressureTrackerTests suites on the fleet at the head (results in comments), and the idle bench above.
• Not run: a capture of the popover in this description. The host-pressure tour (scripts/cmux-next/media/tours/host-pressure.json) now turns the toggle on first.

No capture: a Debug-only surface that is off by default (hostPressure.enabled); the host-pressure tour drives it for design review.

Takes back #24298: only its plans/cmux-next/idle-wakeups.md row, which part 1 wrote and this part 2 extends with the toggle and window stop condition, and the 5-line HostPressureMonitor.start(while:) guard; part 1's behaviour is otherwise unchanged.

Fast gates note: its Sidebar-Look finding names 163 CmuxNextSidebar/Views files this PR never touches. The job checks out at --depth=2, so the head commit's parent is missing, and git diff-tree --root lists the whole tree as that one commit's change. It's a shallow-checkout artifact of the gate, not this diff.

Leo-ask: ask-427cc7d8f5

Changelog

none (Debug-only, off by default)

Agent session: cosmic-gray

🤖 Generated with Claude Code

[cursor]

Bugbot needs on-demand usage enabled

Bugbot uses usage-based billing for this team and requires on-demand usage to be enabled.

A team admin can enable on-demand usage in the Cursor dashboard.

[github-actions]

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

Review 6bddc84: 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=pr24507 -f ref=app-eff/host-pressure-indicator -f platform=macos -f backend_mode=local

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

Tour of 6bddc84f33 (run)

The path-selected recorder failed for core-after, core-before; see the run artifact and failed manifests.

Path-selected interactions

Interaction	Changed paths
agent-pane	Packages/macOS/CmuxNext/Sources/CmuxNextAgentPane/AcpmuxEnvironment\+HostPressure.swift
core	Packages/macOS/CmuxNext/Sources/CmuxNextApp/HostPressure/HostPressureIndicatorView\+Debug.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/HostPressure/HostPressureIndicatorView.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/HostPressure/HostPressurePopover.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/HostPressure/HostPressureSampling.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/HostPressure/HostPressureService.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/HostPressure/HostPressureStrings.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/HostPressure/HostPressureTunables.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/Settings/DebugSettings.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/Settings/DebugSettingsService.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/WindowRootView\+TitlebarControls.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/WindowRootView.swift Packages/macOS/CmuxNext/Sources/CmuxNextApp/Windows/WindowController\+Sidebar.swift Packages/macOS/CmuxNext/Sources/CmuxNextHostPressure/HostPressureMonitor.swift Packages/macOS/CmuxNext/Tests/CmuxNextAppTests/HostPressureIndicatorTests.swift Packages/macOS/CmuxNext/Tests/CmuxNextHostPressureTests/HostPressureMonitorTests.swift
host-pressure	scripts/cmux\-next/media/tours/host\-pressure.json

agent-pane-before: the media could not be published (refused 3 file(s) that show private names: 24507/6bddc84f/next-agent-pane-before/shots/02-open-agent-chat.png (fleet host name, fleet Mac mini name); 24507/6bddc84f/next-agent-pane-before/shots/03-que)

agent-pane-after: the media could not be published (refused 3 file(s) that show private names: 24507/6bddc84f/next-agent-pane-after/shots/02-open-agent-chat.png (fleet host name, fleet Mac mini name); 24507/6bddc84f/next-agent-pane-after/shots/03-queue)

Core UI (before): FAILED — 16 ok, 3 failed, 1 unavailable

Video (mp4)

#	Step	Result	Command
1	Launch	ok
2	New workspace	ok	cmux workspace new --name Tour
3	Type in the terminal	ok	cmux workspace name:Tour screen current pane current tab current terminal current write --text "echo hello from the cmux-next tour\r"
4	A command reports progress: tab loading spinner	ok	cmux workspace name:Tour screen current pane current tab current terminal current write --text "clear; printf '\\033]9;4;3\\007'; sleep 900\r"
5	Split right	failed: exited 1	cmux action run splitRight
6	Split down	failed: exited 1	cmux action run splitDown
7	New terminal tab	failed: exited 1	cmux action run newSurface
8	Browser tab	ok	cmux tab new-browser --url https://example.com
9	Hide the sidebar	ok	cmux action run toggleSidebar
10	Show the sidebar	ok	cmux action run toggleSidebar
11	Notification	ok	cmux notify --title Tour --body "Hello from CI"
12	Notifications panel	ok	cmux action run showNotifications
13	Agent chat	ok	cmux agent new-chat
14	Agent workspace	ok	cmux workspace new --name Agent
15	Agent starts	ok	cmux workspace name:Agent screen current pane current tab current terminal current write --text "clear; printf '\\033]7501;state=working\\033\\\\'; sleep 8; printf '\\033]7501;state=done\\033\\\\'; sleep 900\r"
16	An agent works: row working spinner	ok	cmux workspace new --name Notes
17	The agent finishes: done mark in the spinner's place	ok
18	Session tree: keycaps on the first rows	ok	cmux settings set sidebar.sessionTree true
19	Session tree back off for later tours	ok	cmux settings set sidebar.sessionTree false
20	Profile menu	unavailable: exited 1 (the menu shot needs a screen capture route)	cmux action run sidebar.profileMenu

Failed steps:

5. Split right


6. Split down


7. New terminal tab

Screenshots (12)

1. Launch


2. New workspace


3. Type in the terminal


4. A command reports progress: tab loading spinner


8. Browser tab


9. Hide the sidebar


11. Notification


12. Notifications panel


13. Agent chat


16. An agent works: row working spinner


17. The agent finishes: done mark in the spinner's place


18. Session tree: keycaps on the first rows

### Core UI \(after\): FAILED — 16 ok, 3 failed, 1 unavailable

Video (mp4)

#	Step	Result	Command
1	Launch	ok
2	New workspace	ok	cmux workspace new --name Tour
3	Type in the terminal	ok	cmux workspace name:Tour screen current pane current tab current terminal current write --text "echo hello from the cmux-next tour\r"
4	A command reports progress: tab loading spinner	ok	cmux workspace name:Tour screen current pane current tab current terminal current write --text "clear; printf '\\033]9;4;3\\007'; sleep 900\r"
5	Split right	failed: exited 1	cmux action run splitRight
6	Split down	failed: exited 1	cmux action run splitDown
7	New terminal tab	failed: exited 1	cmux action run newSurface
8	Browser tab	ok	cmux tab new-browser --url https://example.com
9	Hide the sidebar	ok	cmux action run toggleSidebar
10	Show the sidebar	ok	cmux action run toggleSidebar
11	Notification	ok	cmux notify --title Tour --body "Hello from CI"
12	Notifications panel	ok	cmux action run showNotifications
13	Agent chat	ok	cmux agent new-chat
14	Agent workspace	ok	cmux workspace new --name Agent
15	Agent starts	ok	cmux workspace name:Agent screen current pane current tab current terminal current write --text "clear; printf '\\033]7501;state=working\\033\\\\'; sleep 8; printf '\\033]7501;state=done\\033\\\\'; sleep 900\r"
16	An agent works: row working spinner	ok	cmux workspace new --name Notes
17	The agent finishes: done mark in the spinner's place	ok
18	Session tree: keycaps on the first rows	ok	cmux settings set sidebar.sessionTree true
19	Session tree back off for later tours	ok	cmux settings set sidebar.sessionTree false
20	Profile menu	unavailable: exited 1 (the menu shot needs a screen capture route)	cmux action run sidebar.profileMenu

Failed steps:

5. Split right


6. Split down


7. New terminal tab

Screenshots (12)

1. Launch


2. New workspace


3. Type in the terminal


4. A command reports progress: tab loading spinner


8. Browser tab


9. Hide the sidebar


11. Notification


12. Notifications panel


13. Agent chat


16. An agent works: row working spinner


17. The agent finishes: done mark in the spinner's place


18. Session tree: keycaps on the first rows

### Host pressure indicator and popover \(before\): DEGRADED — 1 ok, 8 unavailable

Video (mp4)

#	Step	Result	Command
1	Launch: the indicator ships off (Debug toggle hostPressure.enabled)	ok
2	Indicator on: a normal host still shows nothing	unavailable: debug.tunables: unknown key (debug.tunables is DEBUG only)
3	Warning: the still gauge after the toolbar band	unavailable: debug.tunables: unknown key (debug.tunables is DEBUG only)
4	The warning's popover: the load against its limit, turns, processes and the busiest sessions	unavailable: debug.host_pressure: debug.host_pressure: {'code': 'method_not_found', 'data': {'app_cli_path': '/Users/cmux/Library/Developer/Xcode/DerivedData/cmux-ci-media-slot0-base/Build/Products/Debug/cmux DEV ci-media-slot0-base.app/Contents/Resources/bin/cmux', 'method': 'debug.host_pressure'}, 'message': "Unknown method debug.host_pressure. A cmux CLI that is older than this app (or from another cmux app) sends methods this app does not have; this app's CLI is /Users/cmux/Library/Developer/Xcode/Derive
5	Closed	unavailable: debug.host_pressure: debug.host_pressure: {'code': 'method_not_found', 'data': {'app_cli_path': '/Users/cmux/Library/Developer/Xcode/DerivedData/cmux-ci-media-slot0-base/Build/Products/Debug/cmux DEV ci-media-slot0-base.app/Contents/Resources/bin/cmux', 'method': 'debug.host_pressure'}, 'message': "Unknown method debug.host_pressure. A cmux CLI that is older than this app (or from another cmux app) sends methods this app does not have; this app's CLI is /Users/cmux/Library/Developer/Xcode/Derive
6	Critical: the triangle, with the cosmic-gray incident's numbers	unavailable: debug.tunables: unknown key (debug.tunables is DEBUG only)
7	The critical popover: acpmux's reasons and the busiest sessions with Stop	unavailable: debug.host_pressure: debug.host_pressure: {'code': 'method_not_found', 'data': {'app_cli_path': '/Users/cmux/Library/Developer/Xcode/DerivedData/cmux-ci-media-slot0-base/Build/Products/Debug/cmux DEV ci-media-slot0-base.app/Contents/Resources/bin/cmux', 'method': 'debug.host_pressure'}, 'message': "Unknown method debug.host_pressure. A cmux CLI that is older than this app (or from another cmux app) sends methods this app does not have; this app's CLI is /Users/cmux/Library/Developer/Xcode/Derive
8	Back to the host's real level	unavailable: debug.tunables: unknown key (debug.tunables is DEBUG only)
9	Indicator off again: no timer, no reads	unavailable: debug.tunables: unknown key (debug.tunables is DEBUG only)

Screenshots (5)

1. Launch: the indicator ships off (Debug toggle hostPressure.enabled)


3. Warning: the still gauge after the toolbar band


4. The warning's popover: the load against its limit, turns, processes and the busiest sessions


6. Critical: the triangle, with the cosmic-gray incident's numbers


7. The critical popover: acpmux's reasons and the busiest sessions with Stop

### Host pressure indicator and popover \(after\): PASS — 9 ok

Video (mp4)

#	Step	Result	Command
1	Launch: the indicator ships off (Debug toggle hostPressure.enabled)	ok
2	Indicator on: a normal host still shows nothing	ok
3	Warning: the still gauge after the toolbar band	ok
4	The warning's popover: the load against its limit, turns, processes and the busiest sessions	ok
5	Closed	ok
6	Critical: the triangle, with the cosmic-gray incident's numbers	ok
7	The critical popover: acpmux's reasons and the busiest sessions with Stop	ok
8	Back to the host's real level	ok
9	Indicator off again: no timer, no reads	ok

Screenshots (5)

1. Launch: the indicator ships off (Debug toggle hostPressure.enabled)


3. Warning: the still gauge after the toolbar band


4. The warning's popover: the load against its limit, turns, processes and the busiest sessions


6. Critical: the triangle, with the cosmic-gray incident's numbers


7. The critical popover: acpmux's reasons and the busiest sessions with Stop

_{Tours are data in scripts/cmux-next/media/tours: add a step or a tour file to show your feature.}

[teamleaderleo]

Owned by app-efficiency on cosmic-gray · session

[blacksmith-sh]

Found 9 test failures on Blacksmith runners:

Failures

Test	View Logs
/tmp/tmpb_r1yu6m/summary-missing.json (live):/summary-missing.json (live):	View Logs
/tmp/tmpoo1hj5l3/summary-fail.json (live):/summary-fail.json (live):	View Logs
[tabs] debug.tab_switch timed 0 of 40 switches/ [tabs] debug.tab_switch timed 0 of 40 switches	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
[tabs] the window draws no frames/[tabs] the window draws no frames	View Logs
test_base_passes (main.NoticesPairTests.test_base_passes)/ test_base_passes (main.NoticesPairTests.test_base_passes)	View Logs
test_targets_outside_the_app_go_to_the_mac_canary (main.SwiftCanaryFleetCoverage.te st_targets_outside_the_app_go_to_the_mac_canary)/ test_targets_outside_the_app_go_to_the_mac_canary (main.SwiftCanaryFleetCoverage.te st_targets_outside_the_app_go_to_the_mac_canary)	View Logs
the committed export failed: check-daemon-capabilities-fresh: plans/cmux-next/ daemon-capabilities.json is stale:	View Logs

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

[teamleaderleo]

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

[teamleaderleo]

rust workspaces / plan (changed Cargo workspaces) is red on 14 of 15 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 16 of 18 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 / cmux-next checks (god files, concurrency, crash safety, l10n) › Checks job structure is red on 13 of 14 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 / cmux-next checks (god files, concurrency, crash safety, l10n) › No new SwiftUI (macOS UI is AppKit) is red on 12 of 13 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 / fast gates is red on 12 of 14 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]

Review (codex gpt-6.1-sol xhigh): SHIP at 6bddc84

Diff-only review (gh pr diff 24507, no checkout) on cmux16, the sixth pass; earlier passes' BLOCKs are fixed (see the description). Its one NOTE is a tour step title that still says "with Stop" for a forced level, which hides Stop; it's left for a follow-up. At this head the fleet ran cmux-ci compile-check --app (passed, job e01cd3d5516370f165afdafb) and HostPressureIndicatorTests,HostPressureMonitorTests,HostPressureTrackerTests (all 3 suites passed).

[teamleaderleo]

Non-green checks at 6bddc84, classified:

• cmux-next checks: the reds are No new SwiftUI, Script tests, Checks job structure and Daemon capabilities export. All four are red on base feat-cmux-next 1549981 too (run 39956788032).
• cmux-next swift test: "no Test run with summary line ... tests started and never finished", the same crash pattern as base 1549981 (job 120424728095). The HostPressure suites passed in this run and on the fleet.
• fast gates / cmux-next fast tier: Sidebar-Look names 163 CmuxNextSidebar/Views files this PR never touches. The same prepush-gate.py --base a30e861 --head <merge> on a full clone reports no new violations, so it's an artifact of the shallow CI checkout.
• release-notary and Guard status: base reds.
• risk evidence: the newest run passes after the Takes back #24298 line.

[github-actions]

The feat-cmux-next push run https://github.com/manaflow-ai/cmux/actions/runs/39958936605 at cfa4d89 failed: cmux-next crash ends the app.
Those jobs last passed at c13e800. This pull request is one of 1 merged since: #24507.
If the failure is in your change, fix forward on feat-cmux-next. Pull requests run only the tiers their paths reach (docs/ci/cmux-next-tiers.md); label a batch PR full-ci to run them all before merging.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.3996179316501 (5b95511089)
• cmux NEXT nightly 1.0.0-nightly.3996289985801 (0b05a9b73b)
• cmux NEXT nightly 1.0.0-nightly.3996409333001 (db407261cc)
• cmux NEXT nightly 1.0.0-nightly.3996498202801 (c541c79190)
• cmux NEXT nightly 1.0.0-nightly.3996659275201 (f751c48608)