Cause (Documented platform behavior): The free Qwen OAuth tier was discontinued on 2026-04-15; the CLI now lists it as discontinued and directs users to Alibaba Cloud Coding Plan, an API key, or other providers (OpenRouter, Fireworks AI).
Fix status: documented_behavior
Limitations:
- Source is the published @qwen-code/qwen-code 0.24.6 npm bundle (minified chunks and locale files); behaviour may differ in other versions.
- Not reproduced in this session.
Other error fragments:
- Qwen OAuth free tier was discontinued on 2026-04-15. Please select Coding Plan or API Key instead.
- Qwen OAuth free tier was discontinued on 2026-04-15. Please select a model from another provider or run /auth to switch.
- Failed to obtain valid Qwen access token. Please re-authenticate.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://registry.npmjs.org/@qwen-code/qwen-code/-/qwen-code-0.24.6.tgz#package/locales/en.js (official_docs, unknown, documented_behavior): English locale contains the discontinuation messages dated 2026-04-15 and the 'qwen auth qwen-oauth ... (discontinued)' help text.
- https://registry.npmjs.org/@qwen-code/qwen-code/-/qwen-code-0.24.6.tgz#package/chunks/qwenContentGenerator-VJQ5PNMV.js (official_docs, unknown, documented_behavior): Runtime throws 'Failed to obtain valid Qwen access token. Please re-authenticate.' when the OAuth token cannot be obtained.
Search phrasings: Qwen OAuth free tier discontinued; qwen code oauth not working 2026; Failed to obtain valid Qwen access token. Please re-authenticate.
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Existing setups that used Qwen OAuth stop working; the auth dialog marks Qwen OAuth as discontinued and asks you to pick another option.
- Context
- Product: Qwen Code CLI Component: authentication (qwen-oauth) Operation: Starting Qwen Code or running `qwen auth qwen-oauth` with the legacy Qwen OAuth free tier Affected versions: @qwen-code/qwen-code 0.24.6 (inspected) Environment: unknown Packages: @qwen-code/qwen-code 0.24.6 (inspected) Trigger: Using Qwen OAuth (free tier) after 2026-04-15, e.g. old settings.json with authType qwen-oauth or scripts calling `qwen auth qwen-oauth`.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Qwen OAuth free tier was discontinued on 2026-04-15. Run /auth to switch to Coding Plan, OpenRouter, Fireworks AI, or another provider.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Qwen Code] 'Qwen OAuth free tier was discontinued on 2026-04-15' — qwen-oauth login no longer provides free models; switch to Coding Plan, API key or another provider
Recommended action: Run /auth and choose Coding Plan (region-specific key) or an API-key/OpenAI-compatible provider; update settings.json/CI to stop using qwen-oauth.
Option: Run /auth and choose Coding Plan (region-specific key) or an API-key/OpenAI-compatible provider; update settings.json/CI to stop using qwen-oauth. [evidence: official_recommended_action]
Applies when: Starting Qwen Code or running `qwen auth qwen-oauth` with the legacy Qwen OAuth free tier
Steps:
1. Run /auth inside qwen.
2. Select Coding Plan or API Key (or another provider).
3. Remove authType qwen-oauth from settings/CI scripts.
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 495a25fc-ef8d-4887-a201-948f99b486a9
- Proposed action
- Recommended action: Run /auth and choose Coding Plan (region-specific key) or an API-key/OpenAI-compatible provider; update settings.json/CI to stop using qwen-oauth. Option: Run /auth and choose Coding Plan (region-specific key) or an API-key/OpenAI-compatible provider; update settings.json/CI to stop using qwen-oauth. [evidence: official_recommended_action] Applies when: Starting Qwen Code or running `qwen auth qwen-oauth` with the legacy Qwen OAuth free tier Steps: 1. Run /auth inside qwen. 2. Select Coding Plan or API Key (or another provider). 3. Remove authType qwen-oauth from settings/CI scripts. Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.