Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Using Cursor 1.4.5 on macOS Sequoia 15.6, I notice that all of my Cursor-related editor tabs, or any non-Cursor editor tab opened at the time a Cursor editor is the active editor, always open in new editor groups. Some examples:
Example 1:
Active editor: Cursor Chat
Double-click myDoc.md in Explorer
Result: myDoc.md is opened in a new editor group (new column to the left of my active editor group)
Example 2:
Active editor: myDoc.md
Open Cursor > Settings… > Cursor Settings
Result: Cursor Settings is opened in a new editor group (same as above)
Example 3:
Active editor: myDoc.md
Double-click myDoc2.md in Explorer
Result: myDoc2.md is opened in the active editor group, to the right of myDoc.md
Example 4:
Active editor: myDoc.md
Open Cursor > Settings… > VSCode Settings
Result: VSCode Settings is opened in the active editor group, to the right of myDoc.md
Is this behavior configurable? I can’t find a configuration setting that would change it—particularly given that it seems to be context-specific to navigating to and away from Cursor editor windows.
Steps to Reproduce
See the steps above in the description. Basically (at least in my environment), opening Cursor editors, or opening any editors when a Cursor editor is active, is hard-wired to create a new editor group.
Expected Behavior
I would expect the default behavior to be reliant on the VSCode editor configuration. I.e. I have “multiple” configured for editor tabs, so I would assume new editors would open within the active editor group. And they do, whenever there’s not a Cursor-based editor driving different behavior.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.5 (Universal)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
Does this stop you from using Cursor
No - Cursor works, but with this issue