Double agent window cause double plan in single chat

Support Help
, ,
1

I’m not sure if this is a bug or…feature.

So, I gave cursor a task in plan mode in “normal” vscode view (I don’t know what it is called these days, sorry, i’m not a vibe coder, so stuck to the old view). The agent was thinking as usual.

Meanwhile I decided to open the new agent window out of curiosity. Opened it via “New agent window” menu. There was the same chat, but it was..kind delayed at first. The same messages appeared in the normal window chat first, than with quite delay in agent window chat.

Than when agent had finished and created a plan, I coudn’t see the plan on the agent window chat. And the last message was different from the normal window chat.

I went back to the normal window and saw that there were two plans tabs. They were similar, but not the same. So I assume the task was duplicated when I opened the agent window.

Is it supposed to be like this?

Local agents. Latest cursor. Grok 4.7 High, Pro subscription if matters.

Request ID from the normal window chat: cb74b1b8-33c0-4137-a159-2ad3cde0aca1

Agent ID from the same chat in the agent window: 1911a32f-692d-4356-b314-cfdb18eda6b1

Version: 3.22.7
VS Code Extension API: 1.128.0
Commit: 37076c6c3f9e253c0fa2305197e45befd13a2260
Date: 2026-09-24T05:01:24.589Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

5

Hey, thanks for the detailed report. No, this shouldn’t happen. This isn’t intended behavior.

When the Agents Window opens, it looks for agents that got interrupted mid-task, like after a crash or restart, and automatically continues them. Your agent was still running in the classic window at that moment, and the Agents Window treated it as interrupted and started it again. That’s why you got two parallel runs of the same task and two similar, but different plans. I’ve passed this to the team.

Until this is fixed, you can work around it in either of these ways:

  1. In the Agents Window: Settings > General > Startup, turn off Continue Interrupted Agents.
  2. Or wait until the agent running in the editor finishes, and only then open the Agents Window.

Both plans come from real runs, so you can keep the one that fits better and close the other tab. Let me know if anything else behaves strangely.