Cursor cloud agents make commits to wrong branch

[Chris_Dekker]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When using multiple cursor background agents on the same repo, I occasionally get a change from one agent thread committed to the branch for another agent. IE, commit designated for branch X committed to branch Y.

Steps to Reproduce

Have not been able to reliably reproduce, but it requires multiple background agents to be active, may be related to quickly changing which agent is in focus in the Web UI.

Expected Behavior

Each agent should be isolated to its own branch

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Using the Web UI for agent management

For AI issues: which model did you use?

Sonnet 4.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

[sanjeed5 (Sanjeed)]

Thanks for reporting this! To help understand this better, could you provide:

1. Request IDs for 1-2 affected agent runs (Chat context menu > Copy Request ID, or use the Web UI’s agent dropdown menu)
2. Exact UI workflow: Were you switching between agent tabs, sending follow-ups, or starting new agents when this occurred?

My hypothesis is this might be a Web UI state management issue when rapidly switching focus, but the diagnostic info will help confirm.

Have you faced this after you reported this later again?

[Chris_Dekker]

Hi Sanjeed,
I don’t have the request ids, but I can confirm item 2. I was switching between agent tabs and sending followups. I typically have 4-5 agents running on the same repo, and I switch between them often and quickly. I was using the https://cursor.com/agents UI when these errors occurred.
I have seen this happen again after submitting the initial report.

[sanjeed5 (Sanjeed)]

Thanks @Chris_Dekker

I’ve passed this on to the team. Would be super helpful if you can share any request IDs when this happen.