AI 程式開發工具
Qwen Code 0.22.3 Lets Chat Channels Retain Eight Named Agent Tasks, but They Still Share a Working Directory
The new Channels feature can retain up to eight named sessions scoped by channel, chat, and sender, and reconnect to the original conversation after a session is closed. This is multi-task management, not parallel isolation: only one task can currently be selected at a time, and all tasks still operate in the same working directory.
Qwen Code 0.22.3 extends the terminal coding agent’s session management to Channels such as Telegram, WeChat, DingTalk, Feishu, and GitHub. The [release notes](https://github.com/QwenLM/qwen-code/releases/tag/v0.22.3) introduce owner-scoped named sessions. With `multiSession` enabled, the same sender can create, select, close, and reopen up to eight named tasks within a chat. Each task retains its own agent conversation and session ID, so users do not have to repeatedly clear the context when switching among PR reviews, test failures, and deployment investigations.
The design deliberately narrows identity scope to the combination of channel, chat, and sender, while task names do not directly expose the underlying session ID. However, the limitations listed in the [Channels documentation](https://qwenlm.github.io/qwen-code-docs/en/users/features/channels/overview/) are important: only one task can currently be selected; a task cannot be switched or closed while it is running or awaiting tool approval; and all named tasks still share the same working directory, with per-task worktrees planned for a later phase. The feature therefore addresses conversation and context switching, not file-level concurrency safety. If two tasks modify the same branch in sequence, they may still overwrite each other’s assumptions or working-tree state.
Multi-session support is limited to daemon-managed Channels and requires `sessionScope: "user"`. It cannot be used when webhooks, group-history backfill, or Channel loops are enabled. Administrators should also pay attention to chat access policies: the default allowlist, pairing codes, and open mode directly determine who can launch agents capable of executing tools.
The same release also tightens input validation when the daemon installs local Extensions: it accepts only absolute paths and rejects relative paths and unsupported options. This reduces path ambiguity caused by changes to the working directory, but it is not comprehensive supply-chain verification. The next point to watch is whether the Qwen team’s planned named cancellation, concurrent switching, and per-task worktrees can extend conversation isolation to processes and the file system.