Qwen Code−50 Strong negative

Operator Insights

What are engineering leaders learning from deploying Qwen Code?

3 accounts: 1 left it or turned it down and 2 evaluated it

Left it or turned it down1

Rolando RojasCo-founderElliptic Marketing
ModelRelay, Elliptic Marketing's open-source router that sends coding-agent requests to several model routes, including Qwen Code's OAuth sign-in.
GitHub (ellipticmarketing/modelrelay), published Apr 16, 2026Read the issue (opens GitHub (ellipticmarketing/modelrelay) in a new tab)
Observation
Elliptic Marketing dropped Qwen Code from its ModelRelay router in April 2026, after Qwen removed the OAuth sign-in ModelRelay used and a user's Qwen entry never came up.
Takeaway
Do not build team tooling on Qwen Code's free OAuth sign-in; plan for a paid Coding Plan or your own model keys.
What happened
On Apr 13, 2026 a user reported that ModelRelay accepted the Qwen Code OAuth credentials but its live dashboard never showed Qwen as up, and pinging, chatting and signing in again did not help. On Apr 16 the co-founder replied that Qwen had removed the ability to use OAuth and that ModelRelay had removed Qwen support in version 1.14.0; his commit that day is titled "Remove the unsupported Qwen Code provider".
- Public engineering write-up
- Removal commit published
Deployment details
ModelRelay, Elliptic Marketing's open-source router that sends coding-agent requests to several model routes, including Qwen Code's OAuth sign-in.
- Public engineering write-up
- Removal commit published
Team
Elliptic Marketing's ModelRelay maintainers
Workload
Routing coding-agent requests through Qwen Code's OAuth credentials
Product version
Qwen Code OAuth sign-in; ModelRelay 1.14.0 removed it

Evaluated it2

Ahmed E. HassanProfessor and Canada Research Chair in Software Analytics, School of ComputingQueen's University
Researchers at Queen's University's School of Computing, running Qwen Code against Qwen3-Next-80B-A3B-Instruct on their own dedicated server.
arXiv (2607.03691v2), published Jul 20, 2026Read the paper (opens arXiv (2607.03691v2) in a new tab)
Observation
Queen's University researchers tested 35 Qwen Code releases on one fixed model and found no significant gain in resolve rate, while the latest releases used up to 19.6% more tokens per task than the per-task baseline.
Takeaway
Pin Qwen Code versions and retest each upgrade on your own tasks, because in this study newer releases spent more tokens for the same or worse resolution.
What happened
Four Queen's researchers held the model fixed and evaluated 35 sequential Qwen Code releases on 50 SWE-bench Verified tasks, with two independent runs per task. The resolve rate fluctuated around a stable mean of 30.5%, its correlation with release order was weak and non-significant, and it peaked at about 39% early and never recovered. The latest releases used up to 19.6% more tokens per task than each task's mean across all versions, while earlier versions ran 24.2% below it.
- Public engineering write-up
- Measured results on stated settings
Deployment details
Researchers at Queen's University's School of Computing, running Qwen Code against Qwen3-Next-80B-A3B-Instruct on their own dedicated server.
- Public engineering write-up
- Measured results on stated settings
Team
Four Queen's University School of Computing researchers
Workload
50 SWE-bench Verified tasks, two runs each, on every release
Product version
35 sequential Qwen Code CLI releases
Model
Qwen3-Next-80B-A3B-Instruct on a dedicated server
Measurement
Resolve rate mean 30.5% with an early peak near 39%; latest releases up to 19.6% more tokens per task

Manifold SecuritySep 1, 2026Manifold Security blogManifold Security tested Qwen Code and found that opening a project folder runs a command the repository's own git config names, at startup and before sign-in. It was still unpatched on 0.22.3 on Sep 1, 2026.
Francisco RosalesOffensive Security EngineerManifold Security
Manifold Security's research team, which tested what CLI coding agents run in the background when they start in a project folder.
Manifold Security blog, published Sep 1, 2026Read the write-up (opens Manifold Security blog in a new tab)
Observation
Manifold Security tested Qwen Code and found that opening a project folder runs a command the repository's own git config names, at startup and before sign-in. It was still unpatched on 0.22.3 on Sep 1, 2026.
Takeaway
Before anyone opens a project that arrived as files, such as a .zip or a shared drive folder, with Qwen Code, inspect its .git/config, and check whether your version still runs git on startup with the repository's config.
What happened
Qwen Code runs git status when it starts, to gather the repository context, and passes the repository's own git config through untouched, so a core.fsmonitor command in that config runs on the host, even before the user has authenticated. Manifold confirmed it on 0.19.6, reported it to Alibaba's security response centre on Jul 7, 2026, where it was accepted, and confirmed it again on 0.22.3 on Sep 1, 2026, unpatched at publication. Cloning, fetching or pulling does not deliver the config: the folder has to arrive with its .git directory inside, and Manifold delivered each of its test repositories as a .zip archive.
Public engineering write-up (security research)
Disclosure dates and versions stated
Deployment details
Manifold Security's research team, which tested what CLI coding agents run in the background when they start in a project folder.
Public engineering write-up (security research)
Disclosure dates and versions stated
Team
Manifold Security research team
Workload
Opening a project folder delivered as a .zip archive with qwen
Product version
Qwen Code 0.19.6, reported Jul 7, 2026; 0.22.3, rechecked Sep 1, 2026

Left it or turned it down1

Elliptic Marketing dropped Qwen Code from its ModelRelay router in April 2026, after Qwen removed the OAuth sign-in ModelRelay used and a user's Qwen entry never came up.

Evaluated it2

Queen's University researchers tested 35 Qwen Code releases on one fixed model and found no significant gain in resolve rate, while the latest releases used up to 19.6% more tokens per task than the per-task baseline.

Manifold Security tested Qwen Code and found that opening a project folder runs a command the repository's own git config names, at startup and before sign-in. It was still unpatched on 0.22.3 on Sep 1, 2026.