New agent view branch change support

I’m really impressed with Cursor 3—it feels like a significant step forward. Great work, team!

I have a workflow question: is there a way to switch branches directly within the new Agent view? Currently, I have to jump to the terminal or editor to change branches, which breaks the flow. It would be a huge quality-of-life improvement to handle this without losing context.

Additionally, it would be great to select a target branch when initializing a new local agent, similar to how it’s handled in the Codex app.

Am I overlooking an existing feature, or do you have any suggestions on how to best adapt my workflow to this new interface?

6 Likes

+1 , I’m feeling the same friction.

My workflow is focused on one project with multiple active branches, not multiple separate projects. I want to be able to switch branches quickly and keep different agents running against different branches, whether through worktrees, local setups, or cloud environments.

Right now, having to leave the Agent view to change branches breaks flow. I’d much rather see branch-level management inside a single project, with all branches visible in the sidebar and the ability to attach agents to each one independently.

That would make it much easier to handle real-world work like continuing a long feature while also shipping a quick fix to dev or juggling multiple parallel branches.

1 Like

Hi @milosz_bednarzak We’re thrilled you’re getting familiar with the new Agents Window in Cursor 3.

Regarding branch selection ease in this view, this is currently in progress so expect updates on this front soon. It is definitely an important piece of the puzzle. Right now, the best option is to start a new chat and select the appropriate branch.

1 Like

Right now, the best option is to start a new chat and select the appropriate branch.

I don’t think that’s possible right now.

I can’t currently select a branch when creating a new agent. My only options are to check out the branch manually in terminal before starting, or use a worktree and have the agent switch via prompting.

What I want is to be able to pick the branch when creating the chat/agent in the first place. And beyond that, I’d still love to see branch-level navigation in the sidebar for a selected repo, with separate chats attached to each branch.
This would improve my efficiency a bunch!

2 Likes

Agree. Even by starting a new agent, there’s no way to choose a branch. So by pressing the Create PR button, we can’t know what branch it’ll commit changes to.

Also, please consider switching branches for submodules. UI should give this option too.

Yes, I’d love this. Similar to Codex where it has a drop down on the bottom right below the chat text area of starting a new agent. Meanwhile, my workaround has been to add it into all my plans to let cursor know to create a fresh branch off of origin/master which keeps me out of terminal, but still suboptimal.

Totally agree if you could just make the current branch info text to dropdown the same way we have a dropdown for the workspace selector it would be perfect

1 Like

Just want to +1 this. It’s a major headache now.

I would also like to +1 this, I am going to need to downgrade to Cursor 2 as I need to point my agents to specific branches, and it appears the ability to run Cloud agents in the sidebar of the editor has been removed.

+1.

Just to be clear on this: the Agents Window in Cursor 3.1.15 will always create new local agents on the same branch that the last agent was on. So the least bad flows right now are either to:

  • use the terminal every time to switch to main and pull upstream
  • remind the agent every time to do this itself (otherwise it’ll make a mess)
  • only use cloud agents (which are interesting but have their own limitations right now)
  • don’t use the Agents window

Mostly commenting in hope of getting a notification when this is fixed, because it makes it hard to make good use of the Agents Window.