Feature request for product/service
Cursor IDE
Describe the request
Currently, when creating a local worktree (parallel) agent, the system automatically creates a new branch from the current branch and includes all existing changes (both staged and unstaged). In contrast, when starting a cloud agent, I can explicitly choose which branch to start from.
This behavior causes issues in common workflows. For example, I often work directly on the main branch, and when I suddenly need to start a new feature or fix, I use multiple agents (I’m on the Cursor Ultra Plan). When I create a new worktree agent, it inherits all my current branch changes, including unfinished or unrelated work, which leads to problems later.
When I create a PR from that worktree, it frequently includes unintended changes from my current branch and results in conflicts.
Requested Improvement
Please allow users to select the branch when creating a new worktree agent, just like we can when creating a cloud agent. This would help isolate work and avoid cross-branch conflicts.
Additional Issue
The “Apply All” button does not currently include package.json changes when the worktree agent runs npm install something. These changes should be applied automatically to maintain environment consistency, I manually have to ask agent what are the dependencies you’ve installed in the same worktree chat to manually install it.
Screenshot / Screen Recording
Operating System (if it applies)
MacOS