Python debugger Restart does not focus the breakpoint

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Expected: The debugger pauses and automatically shows the breakpoint again.

Actual: After Restart, I have to click the frame in CALL STACK manually to get the normal paused view.

Steps to Reproduce

  1. Create test.py containing print(2) and set a breakpoint on that line.
  2. Press F5 to start debugging. The editor correctly shows the paused line.
  3. Click Restart (Ctrl+Shift+F5).

Screenshots / Screen Recordings

1cf3d56e-ccde-49df-aa0a-aea3e2cdea23.png
1cf3d56e-ccde-49df-aa0a-aea3e2cdea23.png1280×1258 54.7 KB

Operating System

Windows 10/11

Version Information

Environment: Windows, Cursor 3.24.12, Python Debugger extension 2026.6.0.

Does this stop you from using Cursor

No - Cursor works, but with this issue

9

Hey @Wentao_Wu, thanks for the report and the screenshot.

This is a known issue we’re already tracking, and I’ve added your report to it. After a Restart, the program really is paused on your breakpoint (that’s why Call Stack shows it), but the editor doesn’t pick up the paused state, so you don’t get the highlighted line, Variables, or the step buttons until you click the frame.

Until it’s fixed, use Stop (Shift+F5) and then F5 instead of Restart. A freshly started session isn’t affected, so the breakpoint line and Variables show up automatically as usual.