[STILL BROKEN] Browser tab completely unresponsive after moving to new window — over a month ignored, considering switching tools

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I originally reported this bug over a month ago (v2.4.22) and it is STILL not fixed as of the latest updates. After moving a browser tab to a new window inside Cursor IDE, the entire page becomes completely unresponsive — no scrolling, no clicking, no element selection, no console, no CSS inspector. Nothing works.

This is not a minor inconvenience. This completely kills my workflow. Every time I need to test responsive layouts (mobile vs desktop), check my UI in different screen sizes, or use the browser dev tools, Cursor crashes and becomes useless. I have reproduced this on two different machines (notebook and desktop PC), so it is definitely not a local issue.

I am deeply disappointed. Multiple updates have shipped since I first reported this, and not a single one addressed this critical bug. The team seems to be prioritizing new features while leaving a broken core feature completely unattended. This feels disrespectful to paying users who depend on the tool daily.

I am formally warning: if this is not fixed soon, I will be switching to an alternative IDE (Replit or Google Project IDX). I cannot keep losing productivity over a bug that has been sitting in the backlog for over a month. Enough is enough.

Steps to Reproduce

  1. Open Cursor IDE (v2.4.22 or later).
  2. Open a browser tab inside the IDE with any URL (e.g., http://localhost:3000/ or any website).
  3. Right-click the browser tab and select “Move into new window”.
  4. In the new window, try to scroll, click links, or use any dev tools (Select Element, Show Console, Show CSS Inspector).

Result: The entire page is unresponsive. No interactions work whatsoever. Cursor may also crash completely.

Expected Behavior

The browser tab should remain fully interactive after being moved to a new window. Scrolling, clicking, link navigation, and all dev tools (Select Element, Show Console, Show CSS Inspector) should work exactly as they do inside the main Cursor window.

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
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: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
3

Hey, I see this is the same bug you reported in the original thread. The bug is still logged and the team is tracking it. Sorry, I don’t have an ETA yet.

I know this seriously affects your workflow, especially with a multi-monitor setup.

For now, the workaround is still the same. Keep the Browser tab in the main Cursor window, or use an external browser for localhost.

I’ll post updates in the original thread. I’m going to close this one as a duplicate so everything stays in one place.

1 Like