Feature request: Add Qwen.ai oauth support #1183

Open
opened 2026-02-16 17:29:54 -05:00 by yindo · 5 comments
Owner

Originally created by @joshrad-dev on GitHub (Aug 8, 2025).

Originally assigned to: @thdxr on GitHub.

Today, Qwen Code implemented oauth support for the Qwen chat website, giving users 2000 free requests a day with no token limit. This would be great to copy to opencode, giving users a ton of free inference. Original implementation here: https://github.com/QwenLM/qwen-code/pull/225

Originally created by @joshrad-dev on GitHub (Aug 8, 2025). Originally assigned to: @thdxr on GitHub. Today, Qwen Code implemented oauth support for the Qwen chat website, giving users 2000 free requests a day with no token limit. This would be great to copy to opencode, giving users a ton of free inference. Original implementation here: https://github.com/QwenLM/qwen-code/pull/225
Author
Owner

@hrstoyanov commented on GitHub (Aug 8, 2025):

See also https://github.com/sst/opencode/issues/402#issuecomment-3169062490

@hrstoyanov commented on GitHub (Aug 8, 2025): See also https://github.com/sst/opencode/issues/402#issuecomment-3169062490
Author
Owner

@joshrad-dev commented on GitHub (Aug 9, 2025):

I will say though that Google asked Cline to remove the implementation of the Gemini CLI provider as it was against TOS, I don't know if Qwen would do the same thing given that they tend to be more pro-OSS.

https://x.com/cline/status/1939129177807913024

@joshrad-dev commented on GitHub (Aug 9, 2025): I will say though that Google asked Cline to remove the implementation of the Gemini CLI provider as it was against TOS, I don't know if Qwen would do the same thing given that they tend to be more pro-OSS. https://x.com/cline/status/1939129177807913024
Author
Owner

@hrstoyanov commented on GitHub (Aug 10, 2025):

Ah .. that might be a show stopper! Thanks for the info!

Here is what Grok said, which colors it differently though:

Yes, Google did request the Cline team to stop using the Gemini CLI provider in the Cline VS Code extension. This is evident from a GitHub issue discussion on the Cline repository, where a Google employee and Gemini CLI maintainer, Ryan J. Salva, raised concerns about the non-standard integration of Gemini CLI in Cline. Specifically, the issue was that Cline was using the Gemini CLI's OAuth client ID, which effectively impersonated the Gemini CLI and relied on private, unstable APIs. Google expressed concerns about the stability and propriety of this implementation, as it could lead to issues with the private APIs not being guaranteed to remain stable.
The proposed solution from Google was for Cline to create its own OAuth client and use a proper Project ID to enable access to Google's Code Assist API, or to import Gemini CLI as a node package for a cleaner integration. Following this request, the Cline team reverted the Gemini CLI provider integration in their release (Cline v3.18.1), as confirmed in the GitHub thread where a contributor acknowledged Google's request and reverted the changes.
Additionally, a changelog referenced in the GitHub discussion indicates that the Gemini CLI provider was removed because Google explicitly asked the Cline team to do so. The reasons appear to be technical and procedural, centered around the improper use of private APIs and OAuth credentials, rather than any ethical or legal controversy

@hrstoyanov commented on GitHub (Aug 10, 2025): Ah .. that might be a show stopper! Thanks for the info! Here is what Grok said, which colors it differently though: Yes, Google did request the Cline team to stop using the Gemini CLI provider in the Cline VS Code extension. This is evident from a GitHub issue discussion on the Cline repository, where a Google employee and Gemini CLI maintainer, Ryan J. Salva, raised concerns about the non-standard integration of Gemini CLI in Cline. Specifically, the issue was that Cline was using the Gemini CLI's OAuth client ID, which effectively impersonated the Gemini CLI and relied on private, unstable APIs. Google expressed concerns about the stability and propriety of this implementation, as it could lead to issues with the private APIs not being guaranteed to remain stable. The proposed solution from Google was for Cline to create its own OAuth client and use a proper Project ID to enable access to Google's Code Assist API, or to import Gemini CLI as a node package for a cleaner integration. Following this request, the Cline team reverted the Gemini CLI provider integration in their release (Cline v3.18.1), as confirmed in the GitHub thread where a contributor acknowledged Google's request and reverted the changes. Additionally, a changelog referenced in the GitHub discussion indicates that the Gemini CLI provider was removed because Google explicitly asked the Cline team to do so. The reasons appear to be technical and procedural, centered around the improper use of private APIs and OAuth credentials, rather than any ethical or legal controversy
Author
Owner

@geoh commented on GitHub (Oct 15, 2025):

I'll just put this here: https://www.npmjs.com/package/opencode-alibaba-qwen3-auth - enjoy!

@geoh commented on GitHub (Oct 15, 2025): I'll just put this here: https://www.npmjs.com/package/opencode-alibaba-qwen3-auth - enjoy!
Author
Owner

@roman-ryzenadvanced commented on GitHub (Dec 14, 2025):

Hmm
https://github.com/roman-ryzenadvanced/OpenQode-Public-Alpha

@roman-ryzenadvanced commented on GitHub (Dec 14, 2025): Hmm https://github.com/roman-ryzenadvanced/OpenQode-Public-Alpha
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1183