[teamleaderleo]

Fix-forward of a review follow-up on #34427, which made a Cloud send wait for the folder grant from picking Cloud. That is part of Leo's Cloud refusal ask: "what happened here on this build?"

The wait had no time limit and waited on the last Cloud pick's grant, whichever folder that was. So a workspace.useFolder that never answered kept the composer locked forever.

• cloudFolderGrants (cloudRun.ts) keeps grants by folder, spelled the way cloudStartFolder spells them. A Cloud start waits only for the grant of the folder it sends.
• The wait stops at CLOUD_FOLDER_GRANT_WAIT_MS (3 s), and then the start is sent anyway. If the folder still isn't granted, the host's worded "pick the folder" refusal (Cloud start: a start refused on this Mac says why, and marks no step failed #34406) covers it, and the prompt stays in the composer.
• Timer: one setTimeout per waiting send. It is cleared when the grant settles, and it ends by itself at 3 s. A grant leaves the map once it settles.
• grantedCloudStart is the pane's Cloud start, and App.tsx uses it as-is. New tests in cloudRun.test.ts drive that wiring: the start is held until the grant settles, it goes after the time limit when the grant never answers, and it waits only for its own folder's grant. A source check ties App.tsx to the helper.

Risk: small and contained in the Cloud first-send path.

Agent session: agent session

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Bounds the Cloud send's folder-grant wait so a grant that never answers can no longer hold the composer. A Cloud start now waits only for the grant of the folder it sends, and at most 3 seconds before sending anyway; the host's worded refusal still covers a folder that isn't granted.

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

[teamleaderleo]

Owned by an agent session · session

[teamleaderleo]

Review (subagent claude-opus-5-5 medium): SHIP at abaa017

Checked: the folder key matches the cwd that cloud.startChat sends (cloudStartFolder on both paths), the timer is cleared when the grant wins, a rejected grant neither blocks nor goes unhandled, granting is safe to pass as a bare callback, and the tests are sound.
Follow-ups: [follow-up] the App.tsx wiring check uses source-text regexes, so a harmless reformat breaks it.

[github-actions]

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

red: web / Web status; a job it gathers is red on this change (its line here); do not merge until green; see lane-rules
red: web / react-apps-check; a job it gathers is red on this change (its line here); do not merge until green; see lane-rules
red: web / react-apps-check (1); no finished base run on b181d9c to compare; do not merge until green; see lane-rules

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4177134165301 (4a7517355a)
• cmux NEXT nightly 1.0.0-nightly.4177399658201 (443d56f95d)
• cmux NEXT nightly 1.0.0-nightly.4177479261801 (0df62819ad)