Cursor element selector crashing Cursor

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In Cursor’s built-in browser, the “Select Element” tool allows you to select an element. But, instead of adding that element to the chat, it crashes the app. I have to restart it.

Steps to Reproduce

  1. Run a NextJS with yarn
  2. Try to select an element

Expected Behavior

Should not crash when inspecting element

Screenshots / Screen Recordings

SCR-20260326-jnzy.png
SCR-20260326-jnzy.png297×344 23 KB

Operating System

MacOS

Version Information

Version: 2.6.21
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: Darwin arm64 25.3.0

For AI issues: which model did you use?

Composer 2

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report. I can see the screenshot with “The window is not responding” and that confirms the element selector is freezing the main process.

This is a known issue with the element selector in the built-in browser. The team is aware and the bug is logged.

One question, was the browser tab docked inside the main Cursor window, or did you pull it out into a separate window? If it was in a separate window, that’s a known trigger. Workaround: keep the browser tab inside the main window.

If it still crashes even with a docked tab, let me know, that helps us prioritize it.

7

Thanks for the speedy reply.

its a docked tab.

image

1 Like
8

Hi. Colleague is also having a similar issue. Please let us know if we can provide anything to help resolve bugs.

Specifically, when colleague opens Cursor browser in tab (not external tab) and colleague selects element, Cursor crashes.

9

Hey, thanks for confirming. This is a known issue with the element selector, the team is aware, and your report helps us prioritize it.

Could you check which Cursor version your colleague is on, and what OS they’re using? That’ll help with debugging.

@Jack_McGregor thanks for confirming the tab is docked. That means it’s not only an undocked issue. We’ll factor that in too.

Let me know if anything else comes up.