[CRITICAL BUG] Browser Tab Unresponsive After Moving to New Window v2.4.22

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating to version 2.4.22 (VS Code 1.105.1), browser tabs become completely unresponsive when moved into a new window using the right-click “Move into new window” option.

The browser tab works perfectly in the main IDE window but immediately becomes frozen/unresponsive when separated into its own window. Users cannot:

  • Scroll on the page
  • Click on any elements
  • Use inspector tools (Select Element, Show Console, Show CSS Inspector)

This critical issue completely blocks development workflow and occurs consistently across multiple machines (notebook and desktop) on Windows 10/11, affecting both localhost development servers and regular websites.

Steps to Reproduce

STEPS TO REPRODUCE:

  1. Update Cursor IDE to version 2.4.22 (VS Code 1.105.1)
  2. Open a Browser Tab inside the IDE with any URL
  3. Right-click on the browser tab and select “Move into new window”
  4. Attempt to scroll, click, or interact with the page in the new window
  5. Try using the inspector tools

EXPECTED BEHAVIOR:
The browser tab should remain fully interactive with all features working normally (scrolling, clicking, inspector tools).

ACTUAL BEHAVIOR:
The page becomes completely unresponsive. No interaction is possible.

VERSION INFORMATION:

  • Version: 2.4.22 (system setup)
  • VSCode Version: 1.105.1
  • Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
  • Build Type: Stable
  • Electron: 39.2.7
  • Chromium: 142.0.7444.235
  • Node.js: 22.21.1
  • OS: Windows_NT x64 10.0.26200
  • Tested on: Windows 10/11 (notebook and desktop)

Expected Behavior

The browser tab should remain fully interactive after being moved to a new window with all features working normally: scrolling, clicking, and inspector tools (Select Element, Show Console, Show CSS Inspector)

Operating System

Windows 10/11

Version Information

Version: 2.4.22 (system setup)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
Build Type: Stable
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

This issue severely impacts my development workflow. The “Move into new window” feature is essential for splitting my workspace between the IDE and browser preview. Without this functionality, I’m limited in multitasking.

The issue is consistent across multiple machines and browser instances, indicating it is a systematic issue introduced in version 2.4.22.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report. I see you’ve created three reports about the same issue. The main thread is here: Bug: Browser tab unresponsive after moving to new window (v2.4.22)

There’s already a workaround there, and the team is aware of the bug. In short:

Workaround:

  • Keep the Browser tab in the main Cursor window (don’t use “Move into new window”)
  • Or open localhost:3000 in a regular browser

Status: The bug is logged, but there’s no ETA for a fix yet. If there are updates, we’ll post them in the main thread.

I’m closing this thread as a duplicate. Please continue the discussion there if needed.