Qwen Code 1.0: The CLI Became an Agent Harness You Can Embed
Alibaba released Qwen Code 1.0 on November 11, 2026. It merged the agent harness capabilities from Qoder into Qwen Code and open sourced them together under Apache 2.0, so a terminal coding assistant is now an open source agent harness you can embed inside your own software.
AI Stella and Liam are AI hosts with AI-generated voices. About our AI hosts
Key takeaways
- Qwen Code 1.0, released November 11, 2026, merged the agent harness capabilities from Qoder into Qwen Code and open sourced them together under Apache 2.0.
- An agent harness is the machinery around the model: it plans steps, calls tools, and keeps an agent on track across a long task. In 1.0 that machinery can be embedded inside your own software, on an in process, in memory event bus with a unified event model that decouples reasoning from tool execution.
- Trying it is short: install with the standalone script or npm, run qwen in your project, and connect Qwen, an OpenAI compatible provider, Anthropic, Gemini, or a local provider. A VS Code extension is also available in beta.
- The gotchas are real: 1.0 is a Preview branch while the stable branch is retained, the software is free but model usage is billed by your provider, and the free Qwen OAuth tier ended in April 2026.
Show notes
Alibaba released Qwen Code 1.0 on November 11, 2026. It merged the agent harness capabilities from Qoder into Qwen Code and open sourced them together under Apache 2.0. What used to be a terminal coding assistant is now an open source agent harness you can embed inside your own software. In this episode of Agentic Pod, Liam and Stella explain what the harness actually does, how to try it step by step, and the gotchas, from the Preview branch to provider billing.
What we cover:
- What changed in 1.0: the Qoder agent harness now lives inside Qwen Code, open source under Apache 2.0
- What an agent harness is: the machinery that plans steps, calls tools, and keeps an agent on track across a long task
- The design: an in process, in memory event bus growing toward a distributed, multi node, multi session setup, with a unified event model that decouples reasoning from tool execution
- How to try it step by step: standalone install script or npm, run qwen in your project, connect Qwen, an OpenAI compatible provider, Anthropic, Gemini, or a local provider, plus a VS Code extension in beta
- A real workflow: fix a failing test in a messy repo, and the embedded path for building your own agent product on top of the harness
- Gotchas: 1.0 is a Preview branch while the stable branch is retained, the software is free but model usage is billed by your provider, and the free Qwen OAuth tier ended in April 2026
Chapters
Questions answered in this episode
What is Qwen Code 1.0?
The November 11, 2026 release of Alibaba's Qwen Code. It merged the agent harness capabilities from Qoder into Qwen Code and open sourced them together under Apache 2.0, so the terminal coding assistant is now also an embeddable agent harness.
What is an agent harness?
The machinery around the model: it plans steps, calls tools, and keeps an agent on track across a long task. Qwen Code 1.0 lets you embed that machinery inside your own software.
How do I try Qwen Code?
Install it with the standalone install script for Linux and Mac, or with npm. Run qwen in your project folder, connect a provider (Qwen, an OpenAI compatible provider, Anthropic, Gemini, or a local provider), and give it a real task. A VS Code extension is also available in beta.
Is Qwen Code free?
The software is free and open source under Apache 2.0. Model usage is billed by your provider, the free Qwen OAuth tier ended in April 2026, and 1.0 is a Preview branch while the stable branch is retained.
Links & resources
Full transcript
Intro
Hey hey hey, welcome to Agentic Pod! I'm Liam.
And I'm Stella! Liam, Alibaba shipped Qwen Code 1.0 on November 11th, and it is not just a CLI anymore?
Right. Alibaba merged the agent harness from Qoder into Qwen Code, and open sourced the whole thing together.
Wait, the harness from their paid tool, now open source?
Apache 2.0 open source. By the end you will know what changed, how to try it, and the one bill nobody warns you about.
What actually changed in 1.0
Okay, plain words. What is an agent harness?
It is the machinery around the model. It plans the steps, calls the tools, and keeps the agent on track across a long task.
So Qwen Code used to be the terminal assistant itself?
Yes. You ran it in your terminal, it read your code, edited files, and ran commands. Now that same tool is also a harness you can embed inside your own software.
Embed it? Like, build my own agent on top of it?
Exactly. The design starts with an in process, in memory event bus. The plan is to grow toward a distributed, multi node, multi session setup.
That sounds like plumbing talk. Why should I care?
Because the thinking part and the doing part are separate. A unified event model decouples reasoning from tool execution, so you can watch, route, and build on those events. But first, how do you even try it?
How to try it, step by step
Step one, install it. There is a standalone install script for Linux and Mac, or use npm with the qwen code package.
Step two?
Open your project folder, then run the qwen command. First launch asks you to connect a model provider.
Which providers work?
Qwen itself, OpenAI compatible providers, Anthropic, Gemini, and local providers. You pick the brain, the harness stays the same.
Pick your own brain. Very generous of them.
Step three, give it a real task. Ask it to find why a test fails, fix the code, and run the test again. There is also a VS Code extension in beta, if the terminal is not your home. Now, what does a real run actually look like?
A real workflow, terminal and embedded
In the terminal, picture this. You point it at a messy repo and say, fix the failing checkout test, and do not break the other tests.
And it just goes?
It reads the code first. Then it plans the steps, edits one file at a time, runs the tests, and adjusts when a test still fails.
That is the harness keeping it on track.
Right. Now flip it. Say you build tools for your own team. Instead of writing all that planning and tool plumbing yourself, you embed this harness inside your own app.
So my app gets the agent loop, and I bring the model?
That is the idea. You hook into the events, add your own tools, and ship your own agent product on top. Which sounds great, until you hit the limits, and there are real ones...
Gotchas and the honest verdict
Gotchas. Start with the big one.
The 1.0 release is a Preview branch. The stable branch is still there, and the docs say so plainly. Preview means interfaces can still change.
So I keep the stable build around?
Keep it around. Second gotcha, the bill. The software is free and open source, but the model is not. Your provider bills you for the tokens you use.
And the old free tier?
Gone. The free Qwen OAuth tier ended in April 2026. If you remember running it for free, that door closed months ago.
Honest verdict, then. Who is this for?
If you just want a coding assistant, try the preview, but nothing forces a switch today. If you build agents yourself, this is the interesting one. A production used harness, open source, that you can actually embed.
Same take here. The step by step guide is in the description. Would you build your own agent on an open harness like this? Tell us in the comments. See you next time!