This is a core feature - (especially use cases where cursor is being used for any level of QA). This bug has overnight decreased our teams productivity ~3-4x (…if i have to send cursor another screenshot ).
Hi Dean, I’m also having the same problem with the browser. I tried doing what you described to activate it, but it doesn’t work. Let’s hope they fix this feature soon because it was very useful.
You said “but there’s no timeline for a fix yet“ which may suggest “Is in the backlog”, perhaps you should said “not ETA yet but we are working on this.“
I can’t say enough how bad a bug this is to have no timeline. The workaround above DOES NOT WORK. A key feature has been removed due to poor release management.
Cursor has been an amazing tool, kudos to the team up to about 3 months ago, but recently issues like this are going to push people, like myself, a top-tier paying customer, to other platforms like Antigravity. In fact, I have to use that because of this bug.
Same issue on Mac, after updating cursor today to:
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
I removed cursor and all related files and installed from scratch. Still the same issue! Your suggestion did not work either.
Mac Studio M3 Ultra
macOS: Tahoe 26.2
I have now rolled back to previous version (2.3.26) that I had and it shows the Browser Window option again and works fine:
Version: 2.3.26
VSCode Version: 1.105.1
Commit: bdbdd3f2cf698f583c5cdd2a6dc0f5aec4ed5f90
Date: 2026-01-07T07:11:15.842Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
).