AI 編碼工具
Qwen Code 0.23.1/0.23.2 Overhauls Multi-Agent Sessions as Legacy WebUI Package Is Retired
Two consecutive Qwen Code releases consolidate workflows, subagent status, isolated worktrees, and multi-client sessions into the daemon and built-in Web Shell. The upgrade also removes the standalone `@qwen-code/webui`, while remote startup, message backpressure, and session leases must be retested against the new security and reliability semantics.
Qwen Code released version 0.23.1 on September 8, followed by 0.23.2 the next day. The most immediate compatibility change is the retirement of the standalone `@qwen-code/webui` package; the browser interface is now provided by the Web Shell built into `qwen serve`. This is more than a frontend migration: through HTTP, Server-Sent Events, and ACP subprocesses, the daemon allows IDEs, browsers, CI systems, and custom clients to share agent sessions instead of each launching a separate agent process. The [0.23.1 release notes](https://github.com/QwenLM/qwen-code/releases/tag/v0.23.1) introduce session resource directories, tabbed transcripts, dynamic workflow visualization, and status reporting for running subagents.
State management for multi-agent collaboration has also become more explicit. Named tasks can create isolated worktrees; IPC reports rejected messages, assigns expiration times to buffered messages, and enforces session leases to prevent multiple writers from modifying the same conversation simultaneously. Version 0.23.2 goes further by dropping peer messages that arrive too quickly when the receiver is overloaded and notifying the sender, turning what could previously become an unbounded queue into observable backpressure. Failed agents are also recorded in the workflow journal, allowing parent workflows to distinguish between “no result” and work that is still running.
For remote use, version 0.23.2 adds a single-command startup flow with automatic token generation, a same-origin Web Shell, and a pairing QR code. However, the [official daemon documentation](https://qwenlm.github.io/qwen-code-docs/en/users/qwen-serve/) still labels the architecture Stage 1 experimental and positions it for local, single-user, or small-team use. SSE can resume events only within the retention window, and listeners shared across multiple workspaces do not constitute a complete ACL. Existing integrations should revalidate package paths, session ownership, message-dropping behavior, and bearer-token configuration; the WebUI replacement should not be treated as a purely cosmetic interface update.