Auto switching tabs when agent completes work breaks editing flow

[moopoints (Jan Senderek)]

Recently Cursor started auto switching tabs when an agent finishes work, and it is extremely disruptive.

Two concrete cases:

1. When an agent creates a new document for a plan or output, Cursor automatically switches focus to that new tab. If I am in the middle of editing another file, my cursor jumps away and I start typing into the wrong document.

2. The same happens with agent chats. While typing in one chat, Cursor will suddenly switch to a different chat tab when an agent completes its response. I only notice after I have already typed into the wrong place.

This breaks flow, especially when working with multiple agents concurrently, and causes accidental edits in the wrong files or chats. Is this intended behavior? If so, is there a way to disable automatic tab switching and keep focus where the user currently is?

Version: 2.4.27
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

[Colin]

Hey @moopoints!

I think we are, at least, addressing #1 in 2.5.

Parallel agents/plans steal focus when completing - disrupts workflow when reviewing multiple plans

hi, thanks for the feedback! we’ve pushed updates to address both: plans will only steal focus if you are currently focused on the chat generating it. if you are working in another chat or editor, it will just open in the background. plan editors remember scroll position when you go back to them these changes will roll out on nightly tomorrow, and to stable release in 2.5!

@moopoints

The same happens with agent chats. While typing in one chat, Cursor will suddenly switch to a different chat tab when an agent completes its response. I only notice after I have already typed into the wrong place.

This is behavior I’m not familiar with. Is that true even when the output of the other chat isn’t a plan?

[moopoints (Jan Senderek)]

@Colin

This is behavior I’m not familiar with. Is that true even when the output of the other chat isn’t a plan?

Thanks for the quick response, Colin.

Yup, happened to me just now again. Chat 1 was applying fixes while I was focused and writing in Chat 2. As soon as Chat 1 completed its response, Cursor auto-switched to Chat 1, and my text input intended for Chat 2 continued in the chat with Chat 1.

And great to hear about the fix in 2.5. Will keep an eye out for that!

[Colin]

Strange! Am I doing something different from you?

[moopoints (Jan Senderek)]

I am using the “Chat” UI which is where the bug was happening for me. But I believe this might have been fixed with the latest update. I will observe and let you know!

[moopoints (Jan Senderek)]

I take this back. Using Chats and still happening to me every time another Chat completes its output.

Version: 2.4.28
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

[Colin]

@moopoints Please give 2.5 a try if you haven’t already! Would love to know if it persists there for you.