Qwen Code 0.25.1 adds side tasks and clearer approvals
Qwen Code 0.25.1 expands side conversations and makes some agent approvals easier to inspect. The October 11 release also includes fixes for permission boundaries and stalled extension operations. Its long list of managed agent changes needs careful reading, because some background capabilities were enabled in a later development change.
Side conversations reach secondary workspaces
The Web Shell can now create a separate conversation inside a parent session’s trusted secondary workspace, even while the parent is responding. The side task change removes a backend restriction that previously rejected that operation, despite the interface already exposing it.
The child keeps the parent’s context and workspace identity. Its history belongs to that parent and workspace, while its prompts remain outside the parent conversation. This gives developers another place to ask a related question without waiting for the main response to finish.
The scope is specific. Existing exclusions for standalone sessions, the Managed engine and SSH workspaces remain. The change should not be read as support for side tasks in every execution mode.
Clearer inputs before approval
Another change connects Hosted native tool approvals to the captured input of the particular call being reviewed. When the transcript lacks the arguments, the approval card can display the stored preview. Matching arguments already present in the transcript still take priority.
The reader limits previews to 8192 bytes and supplies the complete input size and a truncation flag. The card explains when only part of the input is visible. That distinction matters when an agent proposes a large file change or sends different inputs through the same tool.
Deployments need the compatible Java reader before the new writer. This preview path does not cover MCP approvals or provide general secret redaction, and it does not enable public Hosted Shell access. It improves what an approver can inspect within the supported workflow.
Background work has a separate release boundary
The background Shell and Monitor story moves beyond the release itself. A separate change merged on October 12 enables those capabilities in the main development branch and lets a live background run retain its runtime after the initiating turn finishes. That later merge is not evidence that the capability was enabled in the October 11 package.
The merge also disclosed a restart cleanup gap. If the Harness restarts before a direct session close, a background run can retain its runtime and workspace mount until cleanup through the control plane. The followup issue remained open when checked on October 12. Users evaluating the development branch should account for that limitation.
Smaller fixes with practical consequences
Version 0.25.1 also stops automatic instruction discovery above the Git repository root, prevents permission rules for one MCP server from authorizing another with a colliding identity, and makes extension Git operations fail rather than wait for interactive credentials. These are useful reasons to examine the update even if the newer managed workflows are outside your setup.
Our report on Claude Code’s delegated work controls examines a separate approach to worker context and model selection.
