[teamleaderleo]

Leo, 2026-10-30:

"WHAT GOOD REASON DO WE HAVE IN THE FIRST PLACE TO KEEP THIS STUFF IN FING LABS IF I FING ASKED FOR THESE F***ING FEATURES"

and earlier, on "Turn on Labs in Settings. Cloud first send refuses to run with Labs off.":

"that seems dumb. i dont like putting so much stuff in labs"

What changes

With labs.previewFeatures off (the default):

• The composer's environment picker (design/environment-picker.md) is the agent page's computer control in New Tab and in the chat composer. It has This Mac, My machines and Cloud and VMs sections, ⌥⌘1–9, New Cloud Machine, Open Cloud…, SSH…, Connect Phone…, Add Machine…, and saved environments on New Tab. Before this PR, Labs off gave the plain Computer menu. (App.tsx: environments={preview} becomes environments.)
• Move to Cloud / Bring Back Local in a started chat's picker, and Pause/Resume of a Cloud chat's machine in the chat menu (cloudChat, cloudMachineRows). Before, both needed Labs.
• Sandboxed runs: a new chat's Run as offers Sandboxed (New Cloud Machine's ⌥ face). The app's sandbox.run, the CLI's runs.sandbox.create (cmux run --sandboxed) and vm.agent_key.create no longer refuse with labs_off. The two dead labsOff strings are removed from Runs.xcstrings.
• A fresh home with only this Mac keeps Add Machine… and New Cloud Machine… in the picker after a chat starts, which Computer picker: expose first-computer setup without Labs #27083 provided for the plain menu.

Safety checks that stay (not Labs)

• Cloud allowed by policy (disabledFeatures.contains(.cloud), policyRefusal, mayCallCloud).
• A signed-in account (not_signed_in).
• An explicit pick or command. A paid VM is only created when the person picks New Cloud Machine, Move to Cloud or Sandboxed and sends, or runs cmux run --sandboxed. Nothing creates one automatically. Waiting on or cancelling an existing run stays open whatever the policy says.

What stays behind Labs, and why

labs.previewFeatures still gates the session coverage label in the chat header (a prototype policy detail), Stats, the music player, Click by Hint (Leo, 10-11: "who wants this feature", so opt-in by his call) and the App Store (Leo, 10-27: "remove app store for now"). What's New's palette entry is ungated in #29061. Not touched here: Voice Room (Lawrence's unofficial experiment), labs.machineJoin (its join routes answer only on the dev platform), labs.classicHome (a legacy fallback). Dev-only surfaces stay off by default (cmux#22662).

Overlap

• carry of #26791: cloud.startChat first send #28111 (cloud.startChat first send) removes the Labs checks in CloudChatPick.swift and CloudStartChat*. This PR leaves those files to it.
• Composer Cloud: Cloud as where a new chat runs, its folder default and start progress (fold of #26801, #26920, #26921) #28686 still adds a labs_off check in CloudStartChat.swift; asked there to drop it. Its App.tsx, ComposerContext.tsx and EnvironmentPicker.tsx edits don't touch the lines this PR changes, apart from comments.
• Specs: teamleaderleo/leo-workspace#1883 updates design/environment-picker.md and design/cloud-work-mode.md.

Before / after

Fresh home, New Agent Chat in /tmp, destination picker opened, labs.previewFeatures at its default (off). Real app at 2x on a fleet capture mini, light and dark, with synthetic data (a fresh home). Steps are in the capture marker's state.

Before (base 32761cbcfc64): the plain Computer menu with only Studio Mac, "Add a computer…" and "New Cloud Machine…".

Capture steps-b14387dd83-2x at 32761cbcfc64 (fleet build, capture mini, text checked for private data)

Light	Dark

After (e8e4fce175d7; later commits change only tests): the environment picker. This Mac (Studio Mac, ⌥⌘1, checked), Cloud and VMs (New Cloud Machine… "Keeps working while your Mac sleeps", Open Cloud…), New environment (SSH…, Connect Phone…, Add Machine…), plus New Worktree beside the folder.

Capture steps-b14387dd83-2x at e8e4fce175d7 (fleet build, capture mini, text checked for private data)

Light	Dark

I viewed the after images in both themes. Verdict: it's the picker Lab users already had, one searchable list in decision order with no repeated controls per row, and it fits on screen beside the composer. It would sit fine next to Claude desktop's environment picker.

Validation

• Fleet compile check of the app at e8e4fce175d7: passed (job f3bab27d5885f7cd2a5de26f).
• Webviews, cmux-ci test on Blacksmith/Linux pool: typecheck plus 16 picker, composer, sandbox and New Tab test files. All pass except computer-picker-onboarding, whose last failure (the New Cloud Machine row was below the fold of a 650 px frame) is fixed at the head and passes alone (fleet job 91a45b5defca9d9a657b61d4).
• Tests updated: computer-picker-onboarding (first-computer setup through the environment picker) and menu-pointer-close-focus/composer-location-strip (the control is now named "Environment").
• New Worktree is the control beside the folder in the environment picker, so the agent-pane.start-folder gallery plays click it there and new-tab-warm-first-frame reads it in the location strip (the gallery health and webview own reds at a8506409).

🤖 Generated with Claude Code

Agent session: agent session

[teamleaderleo]

Owned by an agent session · session

[github-actions]

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

Review e9119b7: 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=pr29059 -f ref=lane/cloud-out-of-labs -f platform=macos -f backend_mode=local

Gallery before/after for e9119b7: 16 states rendered, 0 images differ, 2654 more touched states not rendered. Images are in the run's artifact, not on this public PR; the independent review of this head reads them on its own, so the PR needs no hand-made screenshots of these states.

gh run download 41212796027 -R manaflow-ai/cmux -n gallery-advisory-29059-e9119b74c38f28ee0b9646eaa1c34e8f2b10b62a (then read gallery-review.json)

States

State	Theme	Status	Diff	Picked by
agent-pane.chat-width/standard	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.chat-width/standard	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.chat-width/wide	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.chat-width/wide	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.chat-width/wide-blocks	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.chat-width/wide-blocks	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.composer/font-size-chat-14	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-chat-14	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-chat-14	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-chat-14	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-tab-14	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-tab-14	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-chat-21	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-chat-21	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-chat-21	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-chat-21	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-tab-21	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-tab-21	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-chat-28	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-chat-28	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-chat-28	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer/font-size-new-chat-28	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/closed	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/closed	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-menu	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-menu	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-pinned-search	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-pinned-search	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-short-note	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-short-note	Apple System Colors	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-short-note-de	Apple System Colors Light	unchanged	0%	own ComposerContext.tsx
agent-pane.composer-context/folder-short-note-de	Apple System Colors	unchanged	0%	own ComposerContext.tsx

_{Pick other states with a Gallery: entry.id, entry.id/variant line in the PR body.}

Passes: CI passes on e9119b74c3.

CI passes on e9119b74c3 (run 41213161991 attempt 1).

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.

web and size checks: green

Default changes

This pull request changes 1 default at e9119b74c38f (what everyone gets without configuring anything):

• tunable-source.CmuxNextApp/Control/AppControl+VMAgentKey.swift:vmText: "aa12a983a1446a2668e7aac8f3130fb2abd1c99adefe112711847754faf1f963" -> "35643bfdbda4cca63f2286fb306e562ecba2e7016a670ce1d7de1b376ae5530f"

Signed off on this commit by review (codex, router-review).

Merge receipt: merged as 861de783681f with these defaults changed, signed off by review (codex, router-review).

Regenerate the snapshot with python3 scripts/ci/defaults_guard.py snapshot.

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4121789249101 (59157092cd)
• cmux NEXT nightly 1.0.0-nightly.4121934030701 (3c5aa2b2a6)

[blacksmith-sh]

Found 1 test failure on Blacksmith runners:

Failure

Test	View Logs
test_every_listed_hook_is_one_glaeda_released_with_the_check (main.SigningHooksInSt epWithGlaedaTests.test_every_listed_hook_is_one_glaeda_released_with_the_check)/ test_every_listed_hook_is_one_glaeda_released_with_the_check (main.SigningHooksInSt epWithGlaedaTests.test_every_listed_hook_is_one_glaeda_released_with_the_check)	View Logs

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

[teamleaderleo]

Review (codex, router-review): SHIP at 96f7639

Reviewer: codex gpt-6-astra high, fast tier.

Follow-ups: 2. Each lands as an issue in this repo that links this receipt; the lane that opened the PR fixes it forward.

SHIP at 96f7639
Visual verdict: no images; Leo tries the build

1. [P1][follow-up] CloudChatPick.read still requires labs.previewFeatures at CloudChatPick.swift:23. With Labs off, Cloud move/setup silently loses work-mode autosizing and repository suggestions, so Cloud is only partially un-gated despite the PR description.

2. [P2][follow-up] No after screenshots or gallery artifact were supplied (review/images/README.txt).

Follow-ups:

• [P1][follow-up] Remove or explicitly scope the remaining CloudChatPick Labs gate.
• [P2][follow-up] Add after screenshots or gallery captures.

[teamleaderleo]

Review (codex gpt-6.1-sol xhigh, router-review): BLOCK at 6c2e29c

BLOCK at 6c2e29c

Visual verdict: Both after screenshots reviewed. Comparable to Claude’s compact picker; no repeated controls, bloated menu, or clipping.

1. [P1] [blocking] Preserve existing machine-load warnings — App.tsx:11531. With Labs off and “Show Machine Load Warnings” enabled, the Computer menu currently warns about overloaded remote machines. Always enabling environments removes those warnings: ComposerContext calculates them only for menuComputers, while EnvironmentPicker receives raw computers and never renders resource warnings. This regresses a working, default-on feature. Carry the warnings into the environment picker; existing warning tests exercise only environments=false.

Validation: Changed TypeScript/TSX files parse, and the Runs catalog is valid with no remaining callers of deleted keys. Full tests were unavailable because Bun, Swift, and project dependencies are absent.

[teamleaderleo]

Review (codex, router-review): SHIP at e4c333a

Reviewer: codex gpt-6-astra high, fast tier.

SHIP at e4c333a

Visual verdict: The environment picker screenshots show no repeated controls, clipping, or off-screen layout.

No correctness findings.

Follow-ups: none

[teamleaderleo]

Review (codex, router-review): SHIP at e9119b7

Reviewer: codex gpt-6.1-sol xhigh, fast tier.

SHIP at e9119b7

Visual verdict: Both after screenshots fit on screen, with clear grouping and no repeated row controls. Comparable to Claude’s environment picker.

No correctness findings. Source and localization checks passed. Runtime tests were unavailable because Bun, Cargo, and dependencies are absent.

Follow-ups: none