Qwen Code’s 3 October nightly release adds a broad set of agent and hosted-workflow features, including workspace-agent collaboration, A2A sharing and isolated remote Qwen runtime hosts. It is a substantial step in the project’s agent capabilities, with the usual nightly-release caveat: these changes are not a promise of a finished, stable experience.
Alibaba Qwen Watch analysis
What happened
The release notes list new workspace-agent collaboration, A2A access and sharing, and isolated remote Qwen runtime hosts. They also describe hosted features including durable remote shell results, file history and undo, and tool approvals. This is a nightly build, not a stable-release announcement.
Other additions include an IMAP and SMTP email channel, concurrent Bash calls in Code Mode, and freeform input in Code Mode. The Qwen Code release notes give the full change list.
Our top picks
- Workspace agents can collaborate
The release adds local workspace-agent collaboration, giving teams a new way to divide work between agents. - Agents can be shared through A2A
New A2A access and sharing extends workspace agents beyond a single local setup. - Remote Qwen runtimes get isolation
Isolated remote runtime hosts give developers another way to run agent workloads away from their local machine. - Hosted sessions gain file history and undo
The notes add hosted file history and undo, useful when an agent’s edits need retracing or reversing. - Code Mode can run Bash calls concurrently
Concurrent calls can let Code Mode handle independent shell work without queuing each command behind the last.
Why it matters
Taken together, these changes point towards Qwen Code supporting more than a coding assistant on one workstation: collaboration between workspace agents, remote runtimes and richer hosted-session controls all appear in the same nightly build. For developers, that means more options to test agent workflows across local and hosted environments.
The release notes establish what was added to this build, not how reliable or broadly available each feature is. Nightly means opportunity, with a side order of rough edges.
Our read
There is enough here to merit a closer look, especially for developers already experimenting with Qwen Code agents. The practical move is to treat this as a test build: try the features that matter to your workflow, but do not mistake a busy changelog for a stability guarantee.
What to watch
- Which of these features make it into a stable release, and with what changes.
- How the project documents setup and limits for remote runtimes and hosted sessions.
- Whether workspace-agent collaboration and A2A sharing prove useful in real development workflows.
Discussion spark: Should agent tools prioritise adding collaboration and hosted capabilities quickly in nightly builds, or wait until those workflows are more polished?
Sources and evidence
- Release v0.24.7-nightly.20261003.2c591ecc08 (3 October 2026, 22:49 UTC)
not affiliated with or endorsed by Qwen