Hey, this is most likely a Flutter or Dart extension issue rather than Cursor itself. Device detection is handled entirely by that extension, and Cursor uses the standard VS Code debug infrastructure here.
A few checks to narrow it down:
- Open View > Output, switch to the Flutter and Dart channels, and look for any errors there.
- Verify
dart.flutterSdkPathis set correctly in Settings with the full path to your Flutter SDK. - Try
Cmd+Shift+P>Flutter: Select Deviceand see if devices show up there. - Try rolling back the Flutter and Dart extensions to earlier versions. Click the gear icon on each extension, then Install Another Version. A similar issue was resolved this way: Flutter debug always disconnect in version 0.40.4
Also, please share:
flutter doctor -voutputflutter devicesoutputadb devicesoutput if you’re using an Android emulator- Installed Flutter and Dart extension versions in Cursor
One more thing. Your description says macOS Intel, but system info shows Darwin arm64. Can you confirm which one it actually is?
With those details, it should be straightforward to pinpoint the cause.