OAuth session persists after switching to Coding Plan API key, causing 401 authentication errors

[irfndi]

Environment

• Qwen Code version: latest
• Operating System: MacOS
• Authentication: Initially OAuth → switched to Coding Plan API key

Steps to Reproduce

1. Authenticate with Qwen Code via OAuth using account A
2. Use the service until hitting free usage limits
3. Purchase Coding Plan and add the new API key via /auth
4. Authentication shows success with the new API key
5. Attempt to continue the existing session or start a new conversation
6. Receive error: ✕ [API Error: 401 invalid access token or token expired]
7. Even after attempting to /auth via OAuth to a different account, the error persists

Expected Behavior

After successfully adding a new Coding Plan API key via /auth, the system should use the new API key for all subsequent requests and allow continued usage.

Actual Behavior

The system continues to use the old OAuth tokens instead of the new API key, resulting in 401 authentication errors. The authentication state appears to be sticky and doesn't properly switch from OAuth to API key authentication.

Additional Context

• The issue occurs when transitioning from OAuth-based free usage to Coding Plan API key usage
• Both accounts (original OAuth and attempted new OAuth) seem affected
• This suggests the authentication context/session is not properly cleared or refreshed when switching auth methods
• The error persists across attempts to re-authenticate
• Change model still appears error -> ✕ [API Error: Qwen API quota exceeded: Your Qwen API quota has been exhausted. Please wait for your quota to reset.]
• Any plan add more quotas for users via oauth that subscribe coding plan?

This creates a frustrating user experience where users who upgrade to paid Coding Plan cannot continue using Qwen Code without potentially starting completely fresh.

[Mingholy]

We sincerely apologize for any inconvenience this may cause. I've read carefully the description of this issue and trying to reproduce the issue. This problem is most likely caused by:

• The coding plan API key is issued by ModelStudio, and this API key can only be used with the global/intl endpoint of Bailian. This issue will be fixed by Add Coding Plan Global/Intl region support #1860 within tomorrow hopefully; And if this is the case you're experiencing, a temporary workaround is to replace the https://coding.dashscope.aliyuncs.com/v1 to https://coding-intl.dashscope.aliyuncs.com/v1
• OAuth credentials unexpectedly remained after the model switch, which I've not reproduced for now. If the error is Qwen API quota exceeded then it indicates that you're using qwen-oauth, however, coding plan and qwen-oauth are not necessarily related, they are completely separate systems. A screenshot of current effective configuration in /model command UI will help.

We apologize again and will fix this issue as soon as possible.

[Mingholy]

Closing for now. If the issue persists please reopen or inform us.

[VikKalm]

Today I've got the same issue but yesterday all was working fine.

[Snake1323]

Has anyone else solved this problem? Everything was working fine for me yesterday, too, but I've been having this issue since this morning.

[tim2205]

Has anyone else solved this problem? Everything was working fine for me yesterday, too, but I've been having this issue since this morning.

same happened

[chinozza]

hi, same happened too...

[viliamvolosv]

me too

[ArtemKutsan]

same problem

[MonaxGT]

me too

[MadScorpT]

same problem