"Build in Cloud" doesn't respect branch choice

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I’m so frustrated. Just burned like $50-100 (hard to tell because the usage / spending tabs are almost useless) on a build out and then review of a complex plan that I spent days hammering out locally in the IDE, then I passed to a cloud agent for implementation using the “build in cloud” option. But apparently it decided to just build against main branch instead of the one I had selected and built the entire plan against.

Steps to Reproduce

Start a local agent in plan mode on a branch other than main (or whatever your default branch is), then select “Build in Cloud” for the plan. Observe that cloud happily builds against your default branch instead.

Operating System

MacOS

Version Information

Version: 3.7.21
VS Code Extension API: 1.105.1
Commit: 517f696d8ab6c53eb04fbfdaae705cd146bf3460
Date: 2026-06-07T21:46:09.237Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Thanks for the report, @ryanw. We noticed this as well and have opened a ticket to track it.

Could you share how you’d expect this to work? Specifically, would you expect work to continue directly on the checked-out branch, or would you expect to create a new branch off of it?