Unable to debug extensions in 0.2.x

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

2.0 has been a complete disaster for me. Not only is my workflow completely broken, the hack job that has been done to force the Agent / Editor buttons sit in the PRIME place where File should be is infuriating.

However, the worst issue is now it is impossible to develop vscode extensions in Cursor - every time you try to debug your extension - what should happen is a new “Code” window appear, complete with explorer, terminal and Editor.

What happens now is a single, fullscreen pane agent window - you can try and click the “Open in Editor mode” but it breaks everything. It’s a total mess and lost a full day of trying to fix the issues, eventually I went back to 1.6.

It like vibe coding web apps has become the primary focus of the editor - something I rarely use it for.

Steps to Reproduce

Edit extension, choose Run Debugger, New window opens with only “Agent” chat view. Impossible to add any other meaningful views.

Expected Behavior

A clone “Code” editor screen complete with Explorer, Terminal, Side panels, Editor view

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version : 2.0
I dont have it install anymore to grab.

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. This is a critical issue for extension developers.

The debugger window opening in Agent-only mode without the standard Editor/Explorer/Terminal views is definitely a regression in v2.0.

Could you share:

  • A screenshot or screen recording of the incorrect debugger window
  • Any console errors (Help > Toggle Developer Tools > Console tab) when you try to start debugging

I’ll pass this to the team since it blocks a normal development workflow.

1 Like