Swift tooling leaving Xcode

Swift is no longer tied as tightly to Xcode: Apple’s Swift project now ships official editor support for Cursor, VSCodium, and other Visual Studio Code-compatible tools. (swift.org) On April 8, 2026, Swift.org said the official Swift extension had gone live on Open VSX, the open-source registry used by editors that can install Visual Studio Code extensions without Microsoft’s marketplace. Swift.org named Cursor, VSCodium, Amazon Web Services’ Kiro, and Google’s Antigravity as supported destinations. (swift.org) The extension brings code completion, refactoring, debugging, a test explorer, and DocC documentation support to those editors, with language features powered by SourceKit-LSP, Swift’s language server. Swift.org’s setup guide now includes Cursor-specific steps for creating and opening new Swift projects. (swift.org 1) (swift.org 2) Swift has supported Visual Studio Code and command-line workflows for years, but Apple’s own tools page still describes Xcode as the full integrated development environment for building, testing, debugging, and distributing apps on Apple platforms. The new shift is that the same official Swift extension is now easier to install in a broader set of editors. (swift.org) (marketplace.visualstudio.com) That broader editor reach does not remove the harder part of Swift development: the compiler. The official Visual Studio Code extension says most features work best with Swift Package Manager projects, and support for Xcode project files is still limited. (marketplace.visualstudio.com) Separate threads on the Swift Forums show where developers still hit friction, especially in user interface code built with result builders, the syntax system behind much of SwiftUI. In a March 25, 2025 forum post, one developer said compiler errors in those blocks can point to the wrong line and force a manual “bisect” by commenting out chunks of code. (forums.swift.org) Another forum thread from November 2024 described the same pattern in medium-sized SwiftUI code bases: developers said they often reduce a view body to a minimal case and rebuild repeatedly to find the real mistake. Swift’s own compiler-performance guide says compile-time analysis requires “patience” and careful measurement, underscoring that the project treats build speed and diagnostics as active engineering problems. (forums.swift.org) (github.com) The compiler itself is also becoming more modular. The Swift repository says part of the compiler is now written in Swift and can be built in different bootstrapping modes, including a “hosttools” mode that uses an installed Swift toolchain to speed local development. (github.com) Put together, the editor story and the compiler story point in the same direction: Swift is spreading beyond a single Apple-only development surface, even as the language team and developers keep working through compile-time and diagnostics problems that show up most sharply in large interface-heavy projects. (swift.org) (forums.swift.org)