A troubleshooting guide for when Supermaven stops offering inline completions on Swift files in VS Code — covering activation, inline-suggest settings, extension conflicts, and connectivity, step by step.
The problem we are fixing is specific: you type in a Swift file in VS Code and no grayed-out inline suggestions from Supermaven appear.
Before digging in, rule out the obvious mismatch. Supermaven does not run in Xcode, so if you were expecting suggestions in Xcode's editor, that is expected behavior, not a bug.
We are strictly talking about VS Code, JetBrains, or Neovim, where Supermaven is actually installed.
Work through the checks below in order. Each one eliminates a common cause, and most missing-completion cases are resolved within the first few steps.
Doing them in order matters, because the later steps assume the earlier ones already passed. Skipping ahead can leave you chasing a symptom whose real cause was step one.
Look at the VS Code status bar or the Supermaven panel for its state indicator. It should show a ready or connected state.
If it shows a signed-out or inactive state, run the Supermaven sign-in command from the Command Palette and complete the browser authentication flow.
Activation is the most common cause of total silence. If the extension never authenticated, it simply will not produce completions.
After signing in, return to a Swift file and type a predictable line to see whether suggestions resume.
If the indicator briefly connects and then drops back to disconnected, that points at a network or proxy problem rather than a missed sign-in, which we address later in this guide.
Supermaven relies on VS Code's inline suggestion mechanism. If that is turned off, nothing will render even when the extension is healthy.
Open Settings and confirm that the editor inline-suggest option is enabled. Search settings for 'inline suggest' and make sure it is on.
Also check that suggestions are not disabled for the Swift language specifically via a language-scoped setting, which can happen if you previously tuned per-language behavior.
Toggle it off and on again if you are unsure, then reload the window to be certain the change took effect.
Remember that VS Code settings can be overridden per workspace. A setting that looks correct in your user settings may be disabled by a workspace .vscode/settings.json file in the project you have open.
If you have another AI completion extension installed, such as GitHub Copilot, the two can compete over the inline suggestion slot and one may suppress the other.
Temporarily disable the other AI completion extension, reload VS Code, and test whether Supermaven suggestions return.
This is one of the most frequent real-world causes of missing completions, and it deserves a dedicated check. We cover conflicts in depth in a companion troubleshooting guide.
If disabling the other extension fixes it, decide which tool you want as your primary inline provider rather than running both at once.
Other extensions that inject their own inline text — some snippet or alternative-completion tools — can cause the same collision, so include those in your check, not just Copilot.
Check the language indicator in the status bar for the open file. It should read 'Swift'.
If VS Code has the file in Plain Text or the wrong language mode, completion behavior can be inconsistent. Click the language indicator and set it to Swift.
Installing the official Swift extension helps here, because it ensures .swift files are recognized and associated correctly.
Also make sure you actually opened a folder or workspace. Some behaviors are degraded when a single loose file is opened outside any workspace.
An unsaved, untitled buffer with no file extension is a common trap: without a .swift extension the editor cannot infer the language, and completion quality suffers until you save it with the right name.
Supermaven fetches completions from its service, so it needs network access. If you are behind a corporate proxy, VPN, or strict firewall, requests may be blocked.
Confirm you have general internet connectivity, then check whether your network filters outbound connections that the extension needs.
If you use a proxy, ensure VS Code's proxy settings are configured so extensions can reach external services.
A blocked connection typically manifests as the extension appearing installed but never producing suggestions, sometimes with an error state in its status indicator.
Switching networks briefly — for example, off the corporate VPN or onto a personal hotspot — is a fast way to confirm whether the network is the culprit before you dig into proxy configuration.
If the hotspot fixes it, you have narrowed the problem to your primary network's filtering, and the conversation becomes one for your IT team about allowing the extension's outbound traffic.
Document exactly which network states work and which do not. That evidence is far more actionable than a vague report that completions sometimes stop.
Make sure both the Supermaven extension and VS Code itself are up to date. Completion glitches are frequently fixed in updates.
Reload the VS Code window from the Command Palette. A stale extension host is a surprisingly common cause of features quietly not working.
If problems persist, uninstall the Supermaven extension, restart VS Code, and reinstall it, then sign in again.
These three actions — update, reload, reinstall — clear the majority of stubborn cases that survive the earlier checks.
Do them in that order of effort. A reload costs seconds; a reinstall plus re-authentication costs minutes, so save it for when the lighter steps have not helped.
Open VS Code's Output panel and select the Supermaven channel, if available, to look for error messages. Authentication failures and network errors often show up there clearly.
The Developer Tools console can also reveal extension errors, accessible from the Help menu.
If you cannot resolve it, gather the specifics — extension version, VS Code version, and any log output — and consult Supermaven's official support or documentation.
Reporting with concrete details gets you a faster answer than a general 'it does not work,' and it helps confirm whether the issue is local configuration or a service problem.
Before you file anything, glance at the official status or documentation to rule out a temporary service outage, which no amount of local troubleshooting will fix.
Once completions are back, keep the mental model clear. Supermaven authoring lives in VS Code; building, signing, and submitting your iOS app lives in Xcode.
If your real goal was AI help inside Xcode's editor, no amount of Supermaven troubleshooting will produce that, because it is not an Xcode extension.
For the supported editors, the checks above resolve nearly all missing-completion cases: activation, inline settings, conflicts, language mode, connectivity, and freshness.
With suggestions flowing again, get back to writing Swift fast — and keep compiling and testing everything the tool proposes.
And remember that a restored completer changes nothing about your release path: shipping still requires Xcode and an Apple Developer Program membership.
Supermaven has no Xcode extension, so completions never appear there. It works in VS Code, JetBrains IDEs, and Neovim. Use one of those for AI completions and Xcode for building and shipping.
Yes. Running two inline completion providers like Supermaven and Copilot can cause one to suppress the other. Disable the other extension, reload, and test.
VS Code's editor inline-suggest option must be enabled globally and not disabled for the Swift language. Search settings for 'inline suggest' to confirm.
It can. Supermaven fetches completions over the network, so strict firewalls, proxies, or VPNs may block requests. Configure VS Code's proxy settings and verify connectivity.
Confirm Supermaven is signed in and active, then check inline suggestions are enabled, then reload the window. Those three steps resolve most cases.