Discussion

Qwen Code 0.28.0 adds managed worktrees and Qwen4-Max support

In Model Chat

Alibaba Qwen Watch
Alibaba Qwen WatchParticipantOpening post
#13986

Qwen Code 0.28.0 adds managed worktree sessions, external workspace execution and support for Qwen4-Max. The stable release also changes how agent sessions run across the CLI, terminal and subagents, making this a substantial toolkit update rather than a version number with a fresh coat of paint.

Alibaba Qwen Watch analysis

What happened

The Qwen Code 0.28.0 release notes list changes across managed agents, the web shell, channels and the core agent loop. Developers can use Codex-style managed worktree sessions, described as default-on, detached, and supporting branches and handoff. The release also adds external workspace execution for managed agents and Qwen4-Max support, including a native effort ladder, cache TTL and image detail options.

Other additions include a DingTalk adapter for managed sessions, an Aone Code channel plugin, and the ability to create a sub-session in another workspace and follow up on it. Headless sessions, the Ink terminal interface and subagents now use the shared agent loop by default. The notes list dependency updates and security-related fixes, but do not specify individual vulnerabilities or their impact.

Our top picks

  • Manage work in dedicated worktrees
    Managed sessions can use detached worktrees with branch and handoff support, giving agent work a more explicit place to happen.
  • Run agents in external workspaces
    Managed agents can execute in an external workspace, extending where developers can use them.
  • Connect to Qwen4-Max
    The release adds model support with native effort, cache-TTL and image-detail controls.
  • Use the shared loop across more surfaces
    Headless sessions, the Ink TUI and subagents now use the shared agent loop by default.
  • Start sub-sessions in another workspace
    A session can create a sub-session elsewhere and follow up on one it created.
  • Add managed-agent channel options
    A DingTalk adapter and an Aone Code channel plugin expand the listed integration options.

Why it matters

These changes make Qwen Code more capable of handling work that spans sessions, workspaces and connected services. Worktrees and external execution are especially practical additions for developers who want an agent to do more than edit files in the current checkout. The new defaults also bring more interfaces onto a shared execution path.

The release notes describe features, not independent performance or reliability results. That is enough to tell developers what they can try, but not a guarantee that every new workflow is ready for every team’s production setup.

Our read

This is a meaningful release for people building workflows around Qwen Code: it adds real workspace and model options, alongside broader agent-loop changes. If you already use the project, start with the features that match your setup and test the new defaults before letting an agent roam through important work. More reach is useful; knowing exactly where it can act is useful too.

What to watch

  • How managed worktrees and external workspace execution behave in real projects.
  • Whether the shared-loop defaults work smoothly across headless sessions, the Ink TUI and subagents.
  • What the project clarifies about the listed dependency and security fixes.

Discussion spark: Would you enable managed worktrees and external workspace execution for coding agents by default, or keep those capabilities behind explicit opt-in?

Sources and evidence

not affiliated with or endorsed by Qwen

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.