# Qwen Code Subscription Login: Which Account to Use and How to Fix Auth Errors

Qwen Code now accepts a Plus or Pro login, but QwenCloud and Alibaba ModelStudio still use different authentication paths.

By Paras Madan | 2026-11-06

Qwen Code now supports signing in with a Qwen Plus or Pro subscription. If you already pay for QwenCloud or Alibaba ModelStudio, however, that is a different authentication route. Before replacing keys or buying another plan, identify which product you actually have.

The distinction matters because a coding client, a model provider and a subscription are three different things. Qwen Code is the client. It can connect to several providers, and the presence of “Qwen” in an account name does not tell you which credentials that connection expects.

## What changed in Qwen Code 0.26.8

The [November 5 release of Qwen Code 0.26.8](https://github.com/QwenLM/qwen-code/releases/tag/v0.26.8) added subscription support across the CLI, VS Code and Desktop. This guide follows the published setup instructions; it is not a hands-on review of a paid account.

The underlying [subscription implementation](https://github.com/QwenLM/qwen-code/pull/16378) adds browser-based device authorization, credential refresh, membership checks and account-specific model discovery. It also connects subscription inference and built-in web search. That means successful login is only one part of the flow: the client also needs to recognize an eligible plan and load the models available to that account.

An important caveat sits in the implementation's own review notes: native-client and purchase-flow end-to-end verification was still listed as outstanding for that revision. A merged feature and a release entry are evidence that support shipped, not proof that every account, platform and purchase path works without problems.

## Choose the account you actually bought

The current [authentication guide](https://qwenlm.github.io/qwen-code-docs/en/users/configuration/auth/) separates these routes:

| What you have | Authentication route | What the client uses |
| --- | --- | --- |
| Qwen Plus or Pro from chat.qwen.ai | Qwen Account with Subscription | Browser sign-in to the subscribed account |
| QwenCloud Token Plan | QwenCloud, then Token Plan | The matching plan key and platform |
| QwenCloud pay-as-you-go access | QwenCloud, then Standard API Key | A platform API key |
| Alibaba ModelStudio access | Alibaba ModelStudio, then the appropriate plan | A key for that particular service |

QwenCloud asks you to choose China or International explicitly. Its Token Plan and standard API routes use different endpoints. Alibaba ModelStudio is another provider option, not a synonym for the Qwen account subscription.

**Match the account, billing product and connection route before troubleshooting the model.** Changing all three at once makes it harder to tell whether you fixed access or simply moved the request to another bill.

## Sign in with Qwen Plus or Pro

Start by checking the installed version with `qwen --version`. If you are running a version from before subscription support arrived, update through the installation method you already use rather than adding a second installation on top of it.

The [official quickstart](https://qwenlm.github.io/qwen-code-docs/en/users/quickstart/) lists Node.js 22 or later for npm installation. For that installation method, the command is:

```bash
npm install -g @qwen-code/qwen-code@latest
qwen
```

Inside the interactive Qwen Code session, run `/auth`. Choose **Qwen Account with Subscription**, complete the browser sign-in with the account holding your Plus or Pro plan, then return to the client. The quickstart also documents `/doctor` for checking your current configuration.

Keep shell commands and interactive commands separate. `qwen` starts the program in your terminal; `/auth` is entered inside that program. Typing a slash command at an ordinary shell prompt is not the same operation.

Before opening a large repository or asking for code changes, try a small, non-sensitive prompt. The useful result is not merely that the browser says you signed in. Check that the client recognizes the intended account and can complete a model request.

## Diagnose the failure before changing settings

There are several places where this process can fail, and they deserve different responses.

If the subscription option is missing, check the installed client version first. If browser login succeeds but the client does not recognize your plan, compare the signed-in account with the account that purchased it. If you use an API key instead, check the provider, plan and region together rather than assuming that another key with a similar name will work.

A rate-limit message also needs to be distinguished from an authentication failure. Signing in again is not a sensible first response to every rejected request. Read the complete error and any account-status guidance before deciding whether the problem concerns identity, eligibility, quota or request rate.

The subscription implementation includes separate guidance for authentication, quota and rate-limit failures. It does not establish one universal allowance for every account. **Do not treat a successful subscription login as a promise of unlimited coding usage.** Check the entitlement shown for your actual plan before committing a sustained workload to it.

## Recover a stuck login without wiping your setup

The [troubleshooting documentation](https://qwenlm.github.io/qwen-code-docs/en/users/support/troubleshooting/) describes a specific failure where a saved authentication selection prevents the interface from reopening. Its remedy is to remove only `security.auth.selectedType` from the relevant settings file and restart, so the client can ask for authentication again.

Back up the file before editing it. User settings live in `~/.qwen/settings.json`, while a project can have its own `.qwen/settings.json`. Do not delete the entire configuration directory just to clear a login choice; doing so makes unrelated settings harder to recover.

Certificate errors are a separate problem. The troubleshooting guide recommends using `NODE_EXTRA_CA_CERTS` with the appropriate corporate root certificate when a workplace network inspects TLS. Ask your administrator for the approved certificate rather than disabling certificate verification to make the error disappear.

Some troubleshooting text still discusses the discontinued free OAuth service. That historical flow should not be confused with the new paid subscription route. Use the current authentication page alongside the release version, rather than treating an older OAuth error message as evidence that all browser sign-in is unavailable.

## Keep the working route until the replacement works

For an existing setup, there is little value in turning a new login option into an unnecessary migration. Keep a record of the provider and model that work today, establish that the new route recognizes your entitlement, and only then decide whether it is a better fit.

The practical advantage of subscription login is less credential setup for an eligible account. It does not remove the need to understand who is serving the request and which allowance pays for it. That is the boundary worth keeping visible, especially when several products share the same brand.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help technical teams turn complicated product changes into clear writing that developers can actually use.

[Book a 30-minute call](https://cal.com/paras-madan/30min).