Support for Parallel Tasks with Separate Branches in Cursor

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Hi team,

I’d like to request a feature that would make it easier to work on multiple tasks in parallel using Cursor.

This request is based on the discussion in the following post: Is It Possible to Work on Several Tasks in Parallel with Cursor?

Use Case

In my workflow, I often need to implement a large feature that can be divided into several smaller, independent parts. Ideally, I would like to:

  1. Split the feature into smaller tasks that can be developed separately.
  2. Use Cursor (for example, Parallel Agents) to work on all parts simultaneously.
  3. Have each task correspond to its own Git branch for better isolation and easier pull requests.
  4. Apply code review feedback to each branch individually.

Current Behavior

At the moment, when using the Parallel Agents feature, pressing “Apply” in each agent merges all changes directly into the main branch. There doesn’t seem to be an option to keep each agent’s work confined to its own branch.

Desired Behavior

It would be great if Cursor supported independent branches for each parallel agent so that work on different parts of a feature can proceed simultaneously without affecting the main branch. This would make collaboration and code review much smoother when working on complex features.

Thanks for considering this request!

Operating System (if it applies)

Windows 10/11
MacOS
Linux

7 Likes
Is It Possible to Work on Several Tasks in Parallel with Cursor?
2

I am a Ultra user and this is my #1 feature right now to reduce developer friction. Highly seconded.

I understand by checking out to another branch and THEN clicking apply, it applies the changes to that branch, but that’s one extra thing I need to remember to do. I acknowledge the downsides would be polluting our branches, but we use PRs to track open branches so this is not a problem for us.

An additional feature request: If I were to select an agent on the right, it checks out automatically to that branch/worktree. I understand that’s really confusing for existing users but it would make my life more easier.

Best
Chai

4 Likes
3

Totally seconding on this.

Most of the time, cursor is almost right and it’s hard to pinpoint minor errors, so I often need to apply changes and do a little testing + bug fixing before adding more follow-ups. This destroys the benefits of using the parallel agents.

It doesn’t matter if I’m working on related sub-tasks or unrelated tasks. I can use multiple agents to do a “first run“, but as soon as I need to step into a worktree to get that agent in the right track, the other agets get completely blocked since my main branch has now development code from another agent.

4

Would love to have something like this.

My use case would be this: I want to work, in parallel, on unrelated tasks A and B, in the same repo.

  1. Working on task A on the main repo
  2. create a `git worktree` for task B
  3. Open Cursor twice, in each directory.
  4. Eventually kill/delete/forget worktree B when finished.

Maybe there could be a way to support that in a more natural way within cursor, where Agents now what task/worktree they belong to.