Starting a second agent planning while another is already planning freezes the first and combines both into the second agent

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Starting a second agent planning while another is already planning freezes the first and combines both into the second agent.

I started an agent planning for a front-end UI bug fix, answered a question it asked me, then left it running.

Steps to Reproduce

I started a new agent to enhance a feature, and the first agent froze “Taking longer than usual…” and somehow the second agent combined both and told me it was planning for both requests.

Expected Behavior

Agents have never had context leak between them before, that’s what I was expecting.

Operating System

MacOS

Version Information

Version: 3.4.20 (Universal)
VSCode Version: 1.105.1
Commit: 0cf8b06883f54e26bb4f0fb8647c9500ccb43310
Date: 2026-05-15T02:26:10.351Z
Layout: editor
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
OS: Darwin arm64 25.2.0

For AI issues: add Request ID with privacy disabled

First request ID: 36d1f930-76fa-483a-91c5-19ef993c3d60
Second request ID (the one that “merged” both agents): b24ef879-47a3-4b0a-9c3f-27a1a0ce8861

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Thanks for the detailed report and request IDs. I haven’t been able to reproduce it on our end yet, so two quick questions:

  1. Were you using the Editor or Agents Window when this happened?
  2. Can you reproduce it on demand? If you can get it to happen again, flipping Privacy Mode off (Settings → Privacy) before triggering it would be a huge help. With privacy mode disabled we can see far more on our side and pinpoint where/if things crossed. With it on, we’re flying mostly blind.
7

I haven’t been able to reproduce it again unfortunately. Thanks for the quick reply!