Breakpoints not working with Flutter

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor IDE will ignore breakpoints in my Flutter App run via the IDE Debug UI. The same configuration is working correctly when run in VSCode.

Steps to Reproduce

I could not create a reproducable example and i cannot share my project. But i can confirm that it is working in VSCode:
Version: 1.113.0 (Universal)
Commit: cfbea10c5ffb233ea9177d34726e6056e89913dc
Datum: 2026-03-24T15:07:18+01:00
Electron: 39.8.3
ElectronBuildId: 13620978
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
Betriebssystem: Darwin arm64 25.3.0

Expected Behavior

Starting a Debug Session via Cursor IDE should stop at breakpoins

Operating System

MacOS

Version Information

Version: 2.6.22 (Universal)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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

Additional Information

Maybe this is linked to the previously fixed bug where the debug tools where missing in the Cursor IDE.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report. This is a recurring pattern. Breakpoints work in VS Code but not in Cursor, and it likely comes down to the difference in VS Code base versions. Cursor is on 1.105.1, while your VS Code is 1.113.0.

A few things to check:

  1. Make sure the Dart/Flutter extension in Cursor is the same version as in VS Code. You can check via the Extensions panel. Search for Dart.
  2. Compare your launch.json between both editors. Are they identical?
  3. In Cursor, open the Debug Console during a session. Do you see any errors or warnings when breakpoints are set?
  4. Try adding "debugExternalPackageLibraries": true and or "debugSdkLibraries": true to your launch.json configuration to see if that changes anything.

Also, can you share your launch.json config and the Dart extension version? That would help narrow down whether it’s an extension compatibility issue or something else.

For reference, a similar issue with Node.js was resolved by changing debug.javascript.autoAttachFilter to smart, but that’s specific to the JS debug adapter, not Dart’s.

Let me know what you find.