Opening code-workspace fails to switch to workspace if already open

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In Win 11 File Explorer, when double clicking on a code-workspace file, it appears to fail to open with no feedback from Cursor.

What is really happening is that if the selected Workspace is already open, Cursor will play “dumb” (no insult intended). That is not an acceptable behavior; at a minimum Cursor should bring that workspace to the foreground (switching desktops if needed) and open a pop-up stat states “Workspace is already open.”

This is not the only time that Cursor will silently fail, for no reason. For example if I want to open 4 chat tabs using the “+” button, the IDE will not open any new chat tabs if there is an uninitiated chat tab (chat that has not received a prompt). Again, this is a frustrating behavior.

Steps to Reproduce

  1. Make sure work-space is already open in Cursor and minimized on the task bar.
  2. Navigate to work-space file in Windows 11 File Explorer
  3. Open the work-space file (double click on my system)
  4. Nothing will happen.

Expected Behavior

At least that workspace should be pulled to the top. Having a pop-up stating it is already open would be appropriate, with possibly a check-box that states “Do not show me this again.”

Operating System

Windows 10/11

Version Information

The ghost entry for this text box is wrong. It shows:
Menu → About Cursor → Copy
It should be updated to:
Menu → Help → About Cursor → Copy

Here is the version information:

Version: 2.6.21 (user setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
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: Windows_NT x64 10.0.26100

Additional Information

If Cursor IDE is behind other windows, it should be pulled to the front.
If Cursor IDE is minimized, it should be opened and pulled to the front.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hi @Lance_McQuiddy,

Thanks for reporting this. Cursor does attempt to bring the existing workspace window to the foreground when you open a .code-workspace file that’s already open — but Windows has a well-known platform restriction that prevents applications from stealing focus from the current foreground window in most cases. This is the same behavior you’d see in VS Code, and unfortunately it’s not something Cursor can fully override.

What should happen is a taskbar flash indicating the window needs your attention, though even that may be subtle depending on your system settings.

Regarding the chat tab behavior — Cursor intentionally reuses an empty (uninitiated) chat tab rather than creating a new one alongside it. The existing tab is ready for your next prompt. If you’d like multiple tabs staged ahead of time, you’d need to send at least one message in each to “initialize” them.

I’ve noted your feedback on both points

7

Thanks Mohit. That all makes sense, and I understand the limitations. What about opening a pop-up that simply states, “Cursor Workspace is already open on desktop .”?