A step-by-step guide to installing and configuring Supermaven in VS Code for Swift work, wiring up the Swift extension, and keeping Xcode in the loop for building and shipping your iOS app.
By the end of this guide you will have Supermaven running inside VS Code, offering fast inline completions on your Swift files. You will also have the official Swift extension installed so the editor understands Swift syntax and symbols.
Just as importantly, you will understand the boundary. VS Code plus Supermaven is your authoring environment; Xcode remains your build, sign, and submit environment.
This hybrid is the standard way to use Supermaven for iOS, because Supermaven does not integrate with Xcode's editor.
Budget about fifteen to twenty minutes. Most of the time is downloads and one sign-in, not fiddly configuration.
Nothing here is destructive to your existing Xcode project. You are adding a second editor for authoring, not changing how your app is built.
You need a Mac with Xcode installed from the Mac App Store, since Xcode carries the iOS SDKs, simulators, and the Swift toolchain you ultimately build against.
You need VS Code installed. Download it from the official Visual Studio Code site rather than a third-party mirror.
You need a Supermaven account. A free account is enough to complete this setup and evaluate the tool.
Optionally, confirm the Swift toolchain is available on your machine. Because you installed Xcode, running xcode-select --install and then xcrun swift --version in Terminal is a quick sanity check that Swift is reachable from the command line.
If xcrun reports a Swift version, your command-line toolchain is wired up correctly and VS Code's Swift extension will be able to find it.
Open VS Code and go to the Extensions view. Search for the official Swift extension, maintained by the Swift project, and install it.
This extension provides language support: syntax highlighting, code completion via SourceKit-LSP, diagnostics, and build tasks for Swift packages.
It matters because Supermaven's AI suggestions complement, but do not replace, real language intelligence. Having SourceKit-LSP running means you get accurate symbol information alongside AI predictions.
After installing, open a Swift file or a Swift package folder and confirm you see syntax highlighting and that the language mode in the status bar reads 'Swift'.
If the language mode is wrong, click it and set it to Swift manually. The extension keys much of its behavior off correct language association.
Back in the Extensions view, search for 'Supermaven' and install the official extension. Confirm the publisher is Supermaven before installing, to avoid look-alikes.
Once installed, VS Code will typically prompt you to activate or sign in. If it does not prompt automatically, open the Command Palette and look for Supermaven commands such as a sign-in or activation command.
The extension runs a lightweight local component that talks to the Supermaven service to fetch completions. This is what delivers the low-latency suggestions the tool is known for.
Do not install multiple AI completion extensions at once during setup. Running Supermaven alongside another inline-completion provider can cause conflicting suggestions, which we address in the troubleshooting guides.
If you already have another AI completer installed, consider disabling it for now so this first run is clean and easy to judge.
Trigger the Supermaven sign-in command from the Command Palette. It will open a browser flow to authenticate your account, then return control to VS Code.
After signing in, the status bar or Supermaven panel should indicate that it is active and ready. If you are on the free tier, you are done — completions will start flowing.
If you intend to use the larger context window, this is where you would connect a paid plan. You can always start free and upgrade later without reinstalling.
Confirm activation by checking the Supermaven status indicator. A ready or connected state means the extension has authenticated and can serve completions.
If the indicator stays in a signed-out or disconnected state, the most common cause is a blocked browser redirect or a restrictive network; the sign-in troubleshooting guide covers those cases.
Open a Swift file and start typing something with an obvious continuation, like a SwiftUI View struct with a body property, or a function signature you can predict the body of.
You should see grayed-out inline suggestions appear as you type. Press Tab to accept a full suggestion, or use your editor's partial-accept binding to take just a word or line.
Try it inside a larger file so the context window has material to work with. Supermaven's suggestions improve when it can see your surrounding types and helpers.
If nothing appears, first check that inline suggestions are enabled in VS Code settings and that no other completion provider is suppressing them.
A quick way to force a suggestion is to type a very predictable line, such as the start of a computed property you have written before. If even that produces nothing, move to the troubleshooting checklist.
VS Code and Supermaven get you fast authoring, but they cannot build or run your iOS app on a simulator or device. For that you return to Xcode.
A common pattern is to keep the same project open in both. Author and refactor Swift in VS Code with Supermaven, then build, run, and debug in Xcode.
For Swift packages you can build and test from VS Code's terminal using swift build and swift test, but full iOS app builds — with an app target, storyboard or asset resources, and signing — belong in Xcode.
Remember that only Xcode plus an Apple Developer Program membership can archive, sign, and submit the app to App Store Connect.
Avoid editing the same file simultaneously in both editors. Save in one before switching, so you do not overwrite changes when the other editor reloads the file from disk.
Once completions work, spend a few minutes on ergonomics. Decide whether inline suggestions should trigger automatically everywhere or be more conservative, using VS Code's editor.inlineSuggest settings.
Learn the accept and dismiss keybindings so you can take partial suggestions confidently. The tool is far more pleasant when you can grab a single line without accepting an entire block you did not want.
Consider disabling any other AI completion extension while you evaluate Supermaven, so you are judging it in isolation rather than a blurred combination.
It is also worth learning the word-by-word and line-by-line accept commands, which let you take exactly as much of a suggestion as you trust.
Finally, keep the official Swift extension and Supermaven updated. Extension updates frequently fix completion glitches and improve compatibility.
Do not expect Supermaven to appear in Xcode. It will not, and there is no setting to make it. If you need AI help while inside Xcode, that is a separate class of tool.
Do not expect Supermaven to configure signing, provisioning, or entitlements. Those are Xcode and Apple Developer Program concerns.
Do not expect AI completions to be correct by default. They are drafts. Compile and test every suggestion, especially anything touching concurrency, memory, or security.
Do not expect it to know APIs released after its training, or to reliably avoid deprecated ones. Cross-check anything unfamiliar against Apple's current documentation.
With those expectations set, you now have a fast, capable Swift authoring loop in VS Code backed by Supermaven, and a clean handoff to Xcode for everything Apple requires to ship.
Yes. Xcode is required to build, run on simulators or devices, sign, and submit iOS apps. Supermaven in VS Code only speeds up writing Swift code.
Install the official Swift extension for VS Code, which provides SourceKit-LSP language support. It complements Supermaven's AI completions with accurate symbol information.
You can, but it often causes conflicting or duplicated inline suggestions. During setup and evaluation, keep only Supermaven enabled so you can judge it cleanly.
You can build and test Swift packages from the terminal, but full iOS app targets with signing and resource assets should be built in Xcode.
Yes. A free Supermaven account lets you install, sign in, and get inline completions. You can upgrade later for the larger context window without reinstalling.