Two changelog entries, thirteen days apart, are more interesting to me than the tool itself.

Qwen Code is Alibaba’s open-source terminal coding agent — described in its own README as an alternative optimized for Qwen’s models, with a “Claude Code-like experience”: reads your codebase, runs multi-step sessions, supports Skills and SubAgents, and works through OpenAI/Anthropic/Gemini-compatible APIs or Alibaba’s own Cloud Coding Plan. Framework and model ship together and are meant to co-evolve, which is a reasonable pitch on its own, and it’s genuinely one of the more capable BYOK terminal agents once you’re past the access question.

But here’s the part I actually stopped on, straight from the project’s own news feed:

  • April 2, 2026 — the free OAuth daily quota got cut from 1,000 requests to 100
  • April 15, 2026 — the free tier was discontinued entirely; anyone still on it had to switch to the Alibaba Cloud Coding Plan, OpenRouter, Fireworks AI, or bring their own API key

The code didn’t change in that window. The tool works exactly the same as it did before April 2. What changed was who gets to use it for free, and that happened in two steps close enough together that it reads like access was being wound down deliberately rather than adjusted once and left alone — a soft landing before the hard cutoff, maybe, rather than a single decisive announcement.

I don’t think this makes Qwen Code a bad project — free tiers on infrastructure that costs real money to run are always temporary in some sense, and plenty of tools I’ve covered here monetize similarly once initial growth is established. It’s also worth noting this predates, by a couple of months, Google doing something structurally similar to Gemini CLI: a genuinely open-source coding agent losing its free backend rather than its license. The pattern seems to be repeating across labs, not unique to any one of them.

What it’s a decent reminder of: “open-source” describes the code, not the economics around running it. The repo stays free to read and fork either way. Whether it stays usable for free is a completely separate decision, made on its own schedule, by whoever’s actually paying for the inference underneath it — which is exactly why the BYOK tools I keep coming back to on this site don’t have this specific failure mode. If you’re weighing Qwen Code against something like it, I laid out the actual tradeoffs between a few of the biggest BYOK options here.

npm install -g @qwen-code/qwen-code