[teamleaderleo]

Clicking New Cloud Machine while signed out now keeps the original creation request and destination through hosted sign-in. A successful sign-in continues once into the existing workspace wizard or requested-machine flow. Replacing the pending request, cancelling sign-in, signing out, changing account scope, closing its window, or disabling Cloud prevents stale creation.

The native action owns this handoff for the Computer menu, Add Device, and command palette. Standalone sign-in fallbacks in the agent pane and Add Device are removed so a refused action cannot silently discard the creation intent. Nonperson callers still receive the signed-out refusal.

This supersedes the native continuation portion of #24837, which predates the workspace wizard and allows multiple waiters on one browser-auth attempt to resume creation. Its CLI auto-open changes remain separate.

Requested behavior: “person-initiated sign-in then resume exact newCloudMachine once (cancel/replacement safe).”

The pending continuation has one generation; the action registry owns the sign-in work and records its network wait and failure. Replacement, sign-out, and policy teardown invalidate it; auth completion consumes it before invoking creation. The hosted sign-in attempt owns its existing timeout and cancellation.

Validation

• Exact head 101aab62316d43ca06958746aed3e05ce9b02ac4: cmux-ci step 71597d472155a75226ce8cdf finished with exit 0 on the native fleet.
• CloudSignedOutCreationContinuationTests and CloudWorkspaceSetupLifecycleTests: 19 tests passed across the two suites.
• AgentPaneConnectActionTests: 7 tests passed. Total: 26 test executions across the three filters; the account replacement test covers four cases.
• git diff --check and prepush-gate.py pass; the gate reports only the existing app-size warning. No live browser sign-in was performed; the handoff is exercised through controlled native continuations and the actual action registry.
  No capture: native action continuation and tests only; existing sign-in and workspace wizard presentations are reused.

Changelog

Fixed: New Cloud Machine continues after sign-in without requiring another click or replaying a superseded request.

Agent session: agent session

---

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

---

Summary by cubic

Clicking New Cloud Machine while signed out now holds the original request and resumes creation once after hosted sign-in succeeds, instead of discarding the intent or requiring another click.

• The native action runs through the action registry's effect lifecycle; ActionTrackedWork preserves deferred work and result tasks across the sign-in handoff, so post-auth outcomes surface through the registry.
• Interactive runs keep their normal failure notice, while CLI callers still capture refusals in their action result.
• The chat the request came from is captured when the action runs, since sign-in may finish after focus moved.
• The sign-in's own user-and-team hydration is allowed to finish; account or team change, stale team restoration, request replacement, sign-in cancellation, sign-out, closing the origin window, or disabling Cloud invalidates the pending creation.
• The continuation uses one generation, so a late sign-in result from a superseded attempt can never resume creation.
• Nonperson callers (for example, agents) still receive the signed-out refusal.

Migration

• Removes the multi-waiter continuation behavior from [rd-biz-chief] Resume Cloud setup through sign-in and auto-open the machine #24837; only the last person-initiated attempt resumes.

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

[teamleaderleo]

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

[github-actions]

Default changes

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

• tunable-source.CmuxNextApp/Handlers/CloudHandlers.swift:bind: "bef2994372d16b669a0bef336a852f6b46fff9abd6c646f12dd81d91e205144d" -> "d14a651a72141973d74ef347b3e25e4226d1a6edc2e48c5dd0785519d246dfd8"

Needs a review. It passes with an independent review receipt on this commit: a comment or review whose first line is Review (<reviewer>): SHIP at ac6d357ca9329fae798c641e69d7fc8c79ef06f5, from a member, not a self-review (the newest verdict naming the head decides; a later BLOCK beats an earlier SHIP), or with an approving review on this commit from @lawrencecchen or @austinywang (the call owners in .github/defaults-call-owners.json, never the author). A receipt posted as a review re-runs this check; after a plain comment, re-run it. The needs a call label alone does not pass, and a new push needs a new receipt.

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

[blacksmith-sh]

Found 10 test failures on Blacksmith runners:

Failures

Test	View Logs
--from must install a complete prebuilt tree/ --from must install a complete prebuilt tree	View Logs
/tmp/tmplxjo2pjs/summary-fail.json (live):/summary-fail.json (live):	View Logs
/tmp/tmprdl9xeqa/summary-missing.json (live):/summary-missing.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_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
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.}

[github-actions]

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

Review ac6d357: 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=pr27104 -f ref=cloud-setup-resume-create -f platform=macos -f backend_mode=local

red: cmux-next checks (god files, concurrency, crash safety, l10n); NEW: red check: Prebuilt web bundles install and stamp (+2 more) is not red on the base 6c1a984; do not merge until green; see lane-rules

[teamleaderleo]

Owned by an agent session · session

[teamleaderleo]

Review (codex gpt-6-astra high, fast, via review-router): SHIP at 101aab6

No P1/P2 correctness, regression, security or test coverage findings.

Fleet suites at this head: cmux-ci step 71597d472155a75226ce8cdf (CloudSignedOutCreationContinuationTests, CloudWorkspaceSetupLifecycleTests, AgentPaneConnectActionTests) exit 0.

[teamleaderleo]

Review (codex gpt-6-astra high, fast, via review-router): SHIP at ac6d357

No P1 or P2 findings. This head merges feat-cmux-next (which has #27758, #27862, #26740 and #26568). The conflict resolution keeps the palette actions, keeps this PR's removal of the agent pane's sign-in fallback, and passes #26740's chat pick into bindMachineCreation.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4100960879201 (a6724679c3)
• cmux NEXT nightly 1.0.0-nightly.4101142921301 (e1f81d2af5)