Key findings
- Running local models draws praise in 5 of the 9 counted accounts on it, from a local Qwen3.5-27B on two RTX 3090s to a 3D web game built in two days on a local model. The other 4 criticise how it handles local models.
- Bugs and stalled tasks are raised in 16 accounts, including tasks that stop silently with a local model, failed file writes, lost work in a devcontainer, and HTTP 400 errors on Claude models through an Anthropic key.
- Context use is raised in 5 accounts, from subagents that start near 105,000 tokens to a study that found Qwen Code's first request the largest of five agents.
- The free Qwen OAuth tier ended on April 15, 2026, so accounts that praised free access describe a route that no longer exists.
Run Qwen Code where its practitioners report it works best: as a harness for local Qwen models on your own hardware. Of the 47 public accounts GILD read, published from October 2, 2025 to October 27, 2026, 29 of the 42 that count are negative, with stalled tasks and failed sign-ins recurring in the record; context use is also raised. Most of the 7 company accounts come from companies building Qwen Code into their tools, and 2 hit a proxy or remote sign-in problem. Two university research groups measured it as well.
Who wrote the 47 accounts
The 47 accounts are 24 GitHub issues, 5 GitHub pull requests, 7 Reddit posts on r/LocalLLaMA, 6 Hacker News comments, 2 arXiv papers, 1 DEV Community post, 1 It's FOSS article, and 1 X post. Each names its author, links its page, and records the model or version where the author states one.
38 accounts come from individual builders and 9 speak for a team, a company, or a university research group. Two of the team accounts come from AgentScope's AgentTeams, a project tied to Alibaba Cloud, and count toward nothing. GitHub issues and pull requests tilt the record toward problems and integrations, and the r/LocalLLaMA share toward developers running Qwen Code on their own hardware.
Where it works
Practitioners pair Qwen Code with local Qwen models: one runs a local Qwen3.5-27B on two RTX 3090s for private projects, and another built a 3D web game in two days on a local Qwen 3.8 Flash Next model.
A Hacker News commenter writes that their company runs Qwen Code as its base agent with MCP servers for Jira, Confluence, GitLab, an in-house logs and metrics platform, and Mattermost. Developers of session tools find its JSONL session history follows Claude Code's layout, so their existing adapters read it.
Where teams hit limits
A company running its own Qwen3 service found Qwen Code 0.0.14 ignored no_proxy and could not reach it in October 2025; later comments on the issue report a fix. A team on VS Code Remote SSH found OAuth sign-in cannot complete on remote servers.
Individual builders add 401 errors on Coding Plan and pay-as-you-go keys, an IntelliJ plugin that ignored local models until v0.17.1, and tasks that stop mid-run. Treat each as a test to run on your own setup before rollout.
- Choose a route per engineer and keep Coding Plan keys out of automation.
- Turn off usage statistics and export telemetry to your own backend.
- Test every MCP server, proxy setting, and IDE plugin on your network.
- Watch token use per task and review every change before merge.
Methodology
GILD read the Hacker News, Reddit, GitHub, and X accounts its research missions stored on October 28, 2026, kept those published from 2025 that describe the author's own use of Qwen Code, and coded each account's positions by hand. A second model then checked every account against its stored source, and the 26 that failed were removed. On October 31, 2026, GILD added 18 accounts from practitioners whose role or employer a page states, two of them arXiv studies, each checked by a second model against its stored source. Counts come from those records; accounts about Qwen models in other harnesses and the Qwen team's own posts are left out. The figures describe only the accounts read.
Products in this piece
Sources
- Official documentation
- 4
- Public source
- 7
- QwenLM/qwen-code on GitHub (README)
- Qwen Code docs: Authentication
- Alibaba Cloud Model Studio: Coding Plan overview
- Qwen Code docs: Terms of service and privacy notice
- Hacker News comment on a company running Qwen Code as its base agent with MCP servers (May 30, 2026)
- QwenLM/qwen-code issue #756: no_proxy ignored for a company's in-house Qwen3 service (Oct 2, 2025)
- r/LocalLLaMA: setting up remote server code generation for a team (Mar 5, 2026)
- QwenLM/qwen-code issue #2724: the IntelliJ IDEA 2026.1 plugin ignored local Ollama models until v0.17.1 (Mar 27, 2026)
- QwenLM/qwen-code issue #15660: subagents start with a 105,000-token prompt (Oct 26, 2026)
- r/LocalLLaMA: a coding harness that will not invalidate the context cache at each prompt (Sep 16, 2026)
- r/LocalLLaMA: Qwen-Code CLI free tier ended Apr 15 (Apr 16, 2026)