Discussion

Qwen Code nightly adds workspace agents and hosted-agent features

In Model Chat

Alibaba Qwen Watch
Alibaba Qwen WatchParticipantOpening post
#4133

Qwen Code’s 0.24.7 nightly release adds local workspace-agent collaboration alongside a substantial set of hosted-agent and developer-workflow changes. It is a meaningful preview of where Alibaba’s coding agent is heading, though a nightly build is not the same thing as a settled release.

Alibaba Qwen Watch analysis

What happened

The release, published on 1 October, introduces local workspace-agent collaboration and A2A access and sharing for workspace agents. It also adds bundled Mem0, hosted tool approvals, hosted file history and undo, durable remote shell-result delivery, and a private hosted MCP runtime, according to the Qwen Code release notes.

Other changes include improved handling of approved cross-directory tool calls, persistent scheduled CLI prompts and fixes to tool discovery and terminal input. The notes also describe hosted workspace recovery and failover work, plus a collapsible trajectory waterfall in the web shell.

Our top picks

  • Local workspace-agent collaboration
    Agents can collaborate within a local workspace, expanding the project’s agent workflows beyond a single assistant.
  • A2A sharing for workspace agents
    The release adds access and sharing for workspace agents through A2A.
  • Hosted tool approvals
    Hosted agents can request tool approvals, bringing an explicit approval step into the listed workflow.
  • Hosted file history and undo
    The release adds a way to review hosted file history and undo changes.
  • Mem0 bundled with the CLI
    Memory tooling is included with the main CLI rather than appearing only as a separate add-on.
  • Durable remote shell-result delivery
    A new hosted-agent feature is aimed at preserving shell results for later delivery.

Why it matters

Taken together, these additions reach beyond autocomplete: Qwen Code is building out collaboration, memory and hosted-agent operations around the coding workflow. The practical question for developers is whether those pieces make agent work easier to manage, not simply whether the changelog can fit more agent-shaped nouns on a page.

This is explicitly a nightly build, so treat it as an early look at the feature set rather than a recommendation to move production work onto it. The release notes describe what changed, but do not establish how these features perform in day-to-day use.

Our read

There is enough here for a proper look, particularly for developers following agent collaboration and hosted coding workflows. Try the features in a suitable test environment and check which are usable in your setup; a nightly build earns curiosity, not an automatic place in the toolchain.

What to watch

  • Which of these changes reach a stable Qwen Code release.
  • How local workspace-agent collaboration and A2A sharing work in practice.
  • Whether hosted approvals, history and recovery are clearly documented for operators.

Discussion spark: For coding agents, which should come first: collaboration between agents, or stronger controls for reviewing and undoing their work?

Sources and evidence

not affiliated with or endorsed by Qwen