Repository navigation
Cloud start: a start refused on this Mac says why, and marks no step failed - #34406
Conversation
…failed A Cloud start the pane refused before it reached Cloud (its folder is not one of the tab's, a Send without a gesture) showed "The app refused the agent connection." under a failed "Set up a Cloud machine" step, and logged nothing under app.cloud. - cloudStartEnded words a transport.* refusal by its code: a folder outside the tab's reads "This folder isn't open in this tab; pick it to send it to Cloud.", any other through transportErrors.errorMessage. - Such a refusal sets refusedHere, and the checklist marks no step failed. - AgentPaneHandOff.cloud logs the pane's own refusals under app.cloud. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?id=aid-3bab30503f0b9a7059e5
Bugbot needs on-demand usage enabledBugbot 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. |
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
Gallery before/after for
States
Pick other states with a Not verified: macOS jobs did not run: compile and app tests were skipped on CI passes on Written by Shipped in:
|
|
Review (subagent claude-opus-5-5 medium): SHIP at fd36da4 Checked the Swift logging (isolation, Follow-ups (fixed forward in the follow-up PR on the same area):
|
|
Found 36 test failures on Blacksmith runners: Failures
...and 26 more test failures. View all on Blacksmith
|
…ree (#34415) The New Tab folder chip can name a recent project nobody clicked (NewTabScreen `recent ?? seeded`), and a Cloud send never granted it, so AgentPaneCloudStart.folderInScope refused it as outside the tab's folders. - New Tab: picking Cloud in Run as grants the chip's folder through onProjectPicked (workspace.useFolder), on that click. - Composer: its Run as Cloud row grants the folder sendToCloud names. - folderInScope is not widened; a Cloud default the person never picked still gets the host's refusal, now worded "pick it" (#34406). Follow-ups from the #34406 review: - Web refusedHere uses Swift's list (cloud_attachments, unsupported, unavailable_now, sandbox_busy, sandbox_spent), so an attachment refusal no longer marks "Set up a Cloud machine" failed. - unavailable_now and the sandboxRuns refusal are logged under app.cloud. - A Swift test for AgentPaneHandOff.refusedHere. Agent-Session: https://cmux.com/deeplink/agent?id=aid-3bab30503f0b9a7059e5 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…folder's grant (#34592) Fix-forward of #34427's review follow-up. The Cloud send waited on the last Cloud pick's workspace.useFolder promise with no time limit, so a grant that never answered kept the composer locked. Grants are now kept by folder (cloudFolderGrants), a start waits only for the grant of the folder it sends, and at most CLOUD_FOLDER_GRANT_WAIT_MS (3 s); past that it sends anyway and the host's worded refusal (#34406) covers a folder still not granted. Agent-Session: https://cmux.com/deeplink/agent?id=aid-3bab30503f0b9a7059e5 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light-3x.png)
Leo, on the "The app refused the agent connection." card under a failed "Set up a Cloud machine" step: "what happened here on this build?"
What happened
A Cloud first send from a New Tab chat whose folder chip named a folder that was not one of the pane's folders.
AgentPaneHandOff.cloud(folderInScope) correctly refused it withtransport.path_outside_rootsbefore anything reached Cloud, but:transportFailedMessage("The app refused the agent connection."), whichcloudStartEndedshowed as is;startupChecklistmarks "machine" failed whenever no step began, so the card blamed "Set up a Cloud machine";app.cloud(CloudStartChat never ran), so the log showed no Cloud failure at all.Change
cloudStartEnded: atransport.*code is worded by its code (cloudRefusalText):transport.path_outside_rootsreads "This folder isn't open in this tab; pick it to send it to Cloud." (newcloudStartup.folderNotOpen, 21 locales), any other throughtransportErrors.errorMessage. It setsrefusedHere.startupChecklist: arefusedHerestart marks no step failed.AgentPaneHandOff.cloudlogs the pane's own refusals (transport.*,cloud_attachments,unsupported) underapp.cloud.folderInScopeis not widened. Why the chip's folder was not a root is the follow-up PR (a New Tab recent project nobody clicked is never granted for Cloud).Small, contained fix (light path): one subagent review, tests in
cloudStartProgress.test.tsandCloudStartView.test.tsx.Risk: low. Only the failed Cloud start card's words and step marks change, plus one log line.
Agent session: agent session
🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Makes a Cloud start refused on this Mac show why it was refused, stop blaming the "Set up a Cloud machine" step, and log the refusal under
app.cloud.transport.*refusal now shows reason-specific wording instead of the generic "The app refused the agent connection."; a folder outside the tab reads "This folder isn't open in this tab; pick it to send it to Cloud."app.cloud.Written for commit fd36da4. Summary will update on new commits.