Playbooks · Coding tasks
Qwen Code 0.28 runs one shared agent loop
Written November 17, 2026
Qwen Code 0.28 puts headless sessions, the terminal UI and subagents on the shared agent loop by default, and adds managed worktree sessions.
Qwen Code 0.28.0, dated November 17, 2026 in the v0.28.0 release notes, changes the part of the tool that every surface shares. Headless sessions, the terminal UI and subagents now run on one shared agent loop by default. The notes state at the top that there are no known breaking changes, and nothing in the release asks for a migration. The change still matters, because the loop is where turns, tool calls and stopping behaviour live. When three surfaces share one loop, they share its behaviour too, including its bugs.
Three surfaces, one loop by default
Two entries in the release notes carry the change. Headless sessions and the Ink TUI run on the shared agent loop by default (#17362), and subagents run on it by default as well (#17420). Before 0.28, a person could meet different loop behaviour depending on how a session was started: typed in a terminal, launched without a terminal, or spawned as a subagent inside another session. After the update, the default answer is the same loop in all three places.
For most users the visible effect is consistency. A behaviour learned in the terminal now holds in a headless run, and a fix to the loop lands everywhere at once. The other side of the same coin is reach: a loop bug no longer stays inside one surface. If a headless job starts behaving oddly after the update, the loop is the first place to look, not the job's own flags.
The switches can be forced off, and the path is visible
Two smaller entries make the default manageable. The loop switches can now be forced off, not only on (#17048). A switch that could only force the shared loop on gave an admin no clean way to pin a surface to the older path. Forcing off is the way back when one surface misbehaves on the shared loop. And each surface's resolved agent-loop path is now made visible (#17256), so a person can see which loop a given surface actually ended up on instead of guessing from the version number.
Those two belong together. A default that applies everywhere is reasonable only if it can be overridden per surface, and only if the result of the override can be seen. Version 0.28 brings both halves in the same release as the default itself.
Managed worktree sessions in the web shell
The web shell gains Codex-style managed worktree sessions, on by default, detached, with branch and handoff (#17228), as the notes describe them. A worktree session works in its own checkout, so an agent can make changes without touching the tree a person is standing in. Detached, with branch and handoff, describes how the work comes back: the session runs apart, on its own branch, and the branch is what gets handed over. Because the sessions are on by default, a web-shell user meets this behaviour on the first session after updating, not after finding a setting.
Compaction, the managed channel and a new model
Three more entries are worth knowing. Compaction now retains the latest complete operation (#17141), so when a long session is compacted, the most recent finished piece of work survives instead of being cut midway. The managed channel gains a DingTalk adapter (#17136) and external workspace execution (#15684), which widens where managed sessions can run and how they can be reached. And the release adds Qwen4-Max support (#17513), described in the notes with its native effort levels, cache lifetime and image detail handling.
The rest of the release is a long list of fixes, tests and internal changes across the web shell, the CLI and the managed runtime. None of it changes the story above, and the notes carry the full list for anyone chasing a specific fix.
What to check after updating
- Run one job on each surface. Try the same small task headless, in the terminal and as a subagent. On 0.28 all three should behave the same way, because all three now use the same loop.
- Look at the resolved path. The release makes each surface's agent-loop path visible. Use that view to confirm a surface is on the loop you expect before blaming a job script.
- Keep the forced-off switch in mind. If one surface misbehaves after the update, forcing its loop switch off is the narrowest rollback the release offers.
- Expect worktree sessions in the web shell. They are on by default, so the first web-shell session after updating may already be a detached worktree session with its own branch.
The previous release is covered in Qwen Code 0.27.4: the November 15 build. That page is one build's notes. Version 0.28 is the release that changes what runs underneath all of them.
Related playbooks
- Cloudflare runs the Codex loop in a Durable Object
- Baseline usage before the shared allowance
- How MonoRace flies a drone on one camera and an IMU
- Qwen Code 0.27.4: the November 15 build
Sources
- Qwen Code v0.28.0 release notes — GitHub — the shared agent loop defaults for headless sessions, the Ink TUI and subagents, the forced-off switches, the visible resolved path, managed worktree sessions, compaction, the DingTalk adapter, external workspace execution and Qwen4-Max support.
Back to: Coding playbooks hub · Also: Qwen Code 0.27.4: the November 15 build