[BUG] Connection Failure: Outdated Connection Parameters for Qwen Code SDK

[amieow]

Problem (one or two sentences)

Recent updates to the Qwen Code SDK / Dashscope documentation have rendered current connection implementations non-functional. The client fails to establish a connection, suggesting that the API endpoints, authentication headers, or initialization parameters have changed.

Context (who is affected and when)

happens to user that using qwen code api provider

Reproduction steps

1. Initialize the Qwen/Dashscope client using standard oauth credential path.
2. Attempt to send a request or initialize a chat session.
3. Observe a ConnectionError, 404 Not Found, or Authentication Failed exception.

Expected result

models can connect

Actual result

400 bad request

Variations tried (optional)

No response

App Version

3.51.1

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote-v0]

I'd like to help with this issue, but I need some clarification to narrow down the root cause. The Qwen Code provider involves several moving parts (OAuth token refresh, Dashscope API endpoint, model IDs), and the current report doesn't give enough detail to pinpoint which component is failing.

Could you please provide more details on the following:

1. Exact error response: Can you share the full error message/stack trace from the Roo Code output panel? A 400 Bad Request could come from either the OAuth token endpoint (https://chat.qwen.ai/api/v1/oauth2/token) or the Dashscope completions endpoint (https://dashscope.aliyuncs.com/compatible-mode/v1). Knowing which one fails is critical.

2. Credential file contents (redacted): Does your ~/.qwen/oauth_creds.json file contain a resource_url field? If so, what is the URL (the domain/path, not the token)? The provider uses this to set the base URL.

3. Which model are you using?: qwen3-coder-plus or qwen3-coder-flash, or a custom model ID?

4. How were your credentials generated?: Were they created via the Qwen Code CLI (qwen-code CLI tool)? Have they worked before with a previous version of Roo Code?

5. Qwen Code CLI version: If you're using the Qwen Code CLI, which version are you on? Has the CLI been updated recently?

6. Does the Dashscope API work independently?: Can you make a direct curl request to https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions with your access token and confirm it works outside of Roo Code?

Without this information, there are several possible failure points -- the OAuth client ID (f0304373b74a44d2b584a3fb70ca9e56) could have been rotated, the token endpoint could have changed, or the Dashscope API could have updated its expected request format.

Please tag @roomote in your response with these details, and I'll be able to form a concrete fix plan.