Swift extension does not activate in the glass mode

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After restarting Cursor (following an update to 3.7.36), the official Swift extension never activates in the glass mode. sourcekit-lsp does not start, and there is no swiftlang.swift-vscode output in the extension host logs for the current session.

Steps to Reproduce

  • Open a large iOS/Xcode workspace
  • Have swiftlang.swift-vscode installed and enabled.
  • Restart Cursor (or update to 3.7.36).
  • Open the workspace — optionally stay in Agent/chat without focusing a .swift file in the editor.
  • Check whether SourceKit-LSP starts (Output → “SourceKit Language Server”, or pgrep sourcekit-lsp).

Expected Behavior

  • Swift extension activates on workspace open (via workspaceContains:**/buildServer.json or **/Package.swift) or when a .swift file is opened.
  • SourceKit-LSP starts and provides jump-to-definition, diagnostics, etc.

Screenshots / Screen Recordings

signal-2026-07-29-12-11-17-949.png
signal-2026-07-29-12-11-17-949.png1264×518 56.8 KB

Operating System

MacOS

Version Information

Version: 3.12.17 (Universal)
VS Code Extension API: 1.128.0
Commit: 0fb762053c34788bb7760d5673f8a6d4c8589d50
Date: 2026-07-17T02:53:53.006Z
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.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report and the screenshot. The Swift depends on the ‘LLDB DAP’ extension error is clearly visible. This is a known issue with Swift extension activation in the Agents Window, and we’re tracking it. Reload Window unfortunately won’t help, so it’s not something in your setup. I can’t share a timeline yet, but I’ll post an update in the thread when I have one.

A couple notes about the behavior:

  • In the Agents Window, language extensions are activated lazily, not when you open the workspace, but when you open a .swift file in the editor. If you stay only in the Agent chat and don’t open a code file, SourceKit-LSP won’t start, and that’s expected. Right now, the step where you open a .swift file is blocked by the LLDB DAP error.
  • Workaround for now: use the classic IDE layout for Swift. In that layout, all extensions load and SourceKit-LSP starts normally.

Let me know if anything also doesn’t work in the IDE layout.