Can't get Supermaven to sign in or activate? This guide walks through authentication flows, network and proxy issues, plan activation, and reinstall steps to get completions working again in your editor.
You installed Supermaven, but it will not sign in or activate. The status indicator stays signed-out, the browser flow fails to complete, or the extension never reaches a connected state.
Without successful activation, Supermaven cannot fetch completions, so the tool appears installed but inert.
This is one of the most common first-run problems, and it is almost always about authentication or network access rather than the extension being broken.
Work through the steps below in order to isolate and fix the cause.
The good news is that because the failure is almost never the extension code itself, the fixes are mostly about clearing a blocked handoff or an obstructed network path.
That framing should lower your stress. You are not looking for a bug in the software; you are looking for the one step between your editor and Supermaven's service that is being interrupted.
Most of the time it is a redirect that never returned, a network that filters the connection, or an account that is not in the state you assume. The steps below check each of those in turn.
If activation did not happen automatically after install, do it manually. Open the Command Palette and run the Supermaven sign-in or activation command.
This opens a browser flow where you authenticate your Supermaven account, then hands control back to the editor.
Sometimes the automatic prompt is missed or dismissed, and manually invoking the command is all it takes.
After completing the browser step, return to the editor and check whether the status indicator moves to a connected state.
If you cannot find the command, confirm the extension is actually enabled first — a disabled extension will not register its commands in the palette at all.
The sign-in flow relies on your browser redirecting back to the editor. If that redirect fails, activation stalls even though you authenticated.
Make sure you complete the flow in a standard browser and allow any prompt to open the editor via a link. If a redirect is blocked, activation cannot finish.
On some systems, an unusual default browser or a locked-down environment interferes with the handoff. Try your standard system browser if a redirect never returns you to the editor.
If the browser shows a success page but the editor stays disconnected, move to the connectivity checks below.
Browser extensions that block pop-ups or intercept custom URL schemes can also swallow the redirect, so try the flow with those temporarily disabled if it keeps stalling.
Confirm you can sign in to your Supermaven account on the official website in a browser, independent of the editor.
If your website login fails, the problem is your account credentials, not the extension. Reset your password or resolve the account issue there first.
If you expected paid features and only see free-tier behavior, verify your plan status in your account. Activation of features can lag until the plan is correctly associated.
Getting the account healthy in the browser first removes an entire class of editor-side confusion.
Also confirm you are signing into the same account you expect. Having authenticated with a different email than the one carrying your plan is a surprisingly common source of missing paid features.
Activation and completions require reaching Supermaven's service. Corporate networks, VPNs, and firewalls frequently block this.
Confirm general internet connectivity, then determine whether outbound requests the extension needs are being filtered.
If you are behind a proxy, configure your editor's proxy settings so extensions can make external requests. In VS Code this is the http.proxy setting and related options.
A blocked network is the classic cause of an extension that authenticates in the browser yet never connects in the editor.
Testing on a different network, such as a personal hotspot, is the fastest way to confirm whether your normal network is the obstacle before you invest time in proxy configuration.
Reload the editor window from the Command Palette after any sign-in attempt. A stale extension host can hold an outdated, disconnected state.
Ensure both the Supermaven extension and your editor are updated. Authentication flows occasionally change, and older extension versions can mishandle them.
After updating, run the sign-in command again from a fresh window.
This simple refresh clears a meaningful share of activation problems that survive the earlier steps.
If an update just installed, a full restart of the editor rather than a window reload is worth doing once, since some extension updates only fully take effect on a clean relaunch.
If activation still fails, uninstall the Supermaven extension, restart the editor, and reinstall it.
A clean reinstall clears corrupted local state that can block authentication. After reinstalling, run the sign-in command and complete the browser flow again.
Watch the status indicator move to connected as confirmation. Then test completions in a Swift file to be sure the full pipeline works.
Reinstalling is heavier than the earlier steps, so save it for when reload and update have not helped.
If a reinstall still lands in the same disconnected state, that is strong evidence the cause is external — network, proxy, or account — rather than local extension state, so return to those checks.
Open the Output panel and select the Supermaven channel, if present, to see authentication or network errors spelled out.
The editor's developer tools console can also surface extension errors that explain a failed handoff.
If you are still stuck, collect the extension version, editor version, and any log messages, then contact Supermaven's official support or consult its documentation.
Concrete details make support far faster, and they help distinguish a local configuration problem from a temporary service issue.
Before escalating, check the official site or status page for any ongoing outage, since a service-side problem will resolve on its own and needs no changes on your machine.
Once activation succeeds, verify the whole path by typing in a Swift file and confirming inline suggestions appear.
Keep the boundary in mind: signing in to Supermaven enables AI completions in VS Code, JetBrains, or Neovim, not in Xcode.
And activation, like the tool itself, has nothing to do with shipping. Building, signing, and submitting your iOS app still require Xcode and an Apple Developer Program membership.
With authentication resolved, you have restored the fast completion experience — now get back to writing Swift, and keep verifying what the tool suggests.
If completions still do not appear even though the status shows connected, that is a different problem, and the missing-completions troubleshooting guide picks up exactly where this one leaves off.
The distinction is worth internalizing. Sign-in problems live between your editor and Supermaven's service; missing-completion problems, once you are connected, usually live in editor settings or a conflicting extension.
Knowing which category you are in saves you from repeating the wrong set of fixes.
Usually a blocked redirect or a network restriction. Confirm the browser handoff returns to the editor, check proxy and firewall settings, then reload the editor window.
Open the Command Palette and run the Supermaven sign-in or activation command, then complete the browser authentication flow and confirm the status indicator turns connected.
It can. Supermaven needs to reach its service to activate and fetch completions. Configure your editor's proxy settings and verify outbound access is not filtered.
Verify your plan is correctly associated by logging into your account on the official Supermaven site, then reload the editor and re-run sign-in so the plan is picked up.
No. Activation only enables completions in supported editors like VS Code, JetBrains, and Neovim. Xcode has no Supermaven integration and is where you build and ship.