[Bug] it show errors with LLDB DAP

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I open swift files in agents window, it show errors with LLDB DAP

Steps to Reproduce

  1. Open xcode project repo
  2. Open files explore
  3. Open swift file
  4. Look at the error at the bottom right screen

Expected Behavior

No error

Screenshots / Screen Recordings

Screenshot 2026-07-04 at 04.35.30.png
Screenshot 2026-07-04 at 04.35.30.png734×558 51.4 KB

Operating System

MacOS

Version Information

Version: 3.10.11
VS Code Extension API: 1.125.0
Commit: 4ef9fe3d055f8c4523179a090f14eb835bc3c940
Date: 2026-07-03T04:44:14.398Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey there.

Have a look at this thread!

7

Thanks, I tried. It seem to work

9

Why is lldb-dap not available in Cursor? Was it available before? Cursor seemed to have worked well with the official Swift extension previously.

10

Hi @nmgcursr!

It looks like it wasn’t available when @deanrie posted in December. It looks like it is now.

Screenshot 2026-07-28 at 22.57.02
Screenshot 2026-07-28 at 22.57.02936×398 31.2 KB

Would love to hear from you about how it works if you install it!

11

Hello Colin!

I do have lldb-dap already installed. It still does not work as expected. To be clear: IDE mode works. The Agents Window does not. I do not get error highlights and that toast appears, even after clicking “Reload Window”. In fact, the “Agents Window” seems to greatly diverge from the Visual Studio Code lineage Cursor started with. I’m not sure how compatible it is with the VSCode backing in general, but I do only get that toast in the Agents Window.

12

Thanks for flagging this @nmgcursr! I wasn’t thinking about the Agents Window.

It looks like swiftlang.swift-vscode is on the list of extensions allowed to load in the Agents Window, but llvm-vs-code-extensions.lldb-dap is not. I can reproduce the toast you’re seeing and I’m flagging that for the team!

14

Is “the list of extensions allowed to load in the Agents Window” something controllable on the user side? Or is it baked into the release and unchangable? I, personally, would prefer the ability for the users themselves to make such decisions. Either way, llvm-vs-code-extensions.lldb-dap should likely be allowed by default.

15

It’s baked in, and for performance reasons, we’ll probably keep it that way for a while! The Agent Window also doesn’t have all the same extension points as the IDE. These extensions are primarily loaded for LSP support.

16

Understandable. Regardless, I do think llvm-vs-code-extensions.lldb-dap should be added to the allowlist. Otherwise, having Swift on the allowlist isn’t that helpful as that extension needs lldb-dap for many of its functions.

17

Is there any update on this?

I also have llvm-vs-code-extensions.lldb-dap installed, and I still get the same error in the latest version of Cursor. There are forum posts going back to December 2025 about swift not working in the agents window. Also the docs page that recommends using SweetPad doesn’t work in the Agents Window either: iOS & macOS (Swift) | Cursor Docs

Almost everything I do is in Swift, so being stuck in IDE mode while the Agents Window keeps moving forward is pretty discouraging. If IDE mode stayed on par with Agents Window, this wouldn’t be a big issue.