On this page
An agent pauses for a decision, but the options are not clear enough to choose. Qwen Code 0.27.0 adds Ask for details for that moment in the Web Shell main view, according to its release notes and accompanying PR description. The release was published on November 8, 2026, at 04:45:25 Asia/Shanghai.
Explanation first, answer later
The action opens a side task with a snapshot of the pending question and its options, including whether multiple choices are allowed. It asks for background, the meaning and differences of the options, their implications and risks, and a recommendation. The explanation appears as an HTML preview in the right panel.
The question stays unanswered. The side task does not answer on behalf of the person making the decision, approve permissions or change the main conversation. Answering or ignoring the question still happens in the main view. Repeated clicks for the same pending question focus its existing details tab rather than opening duplicate side tasks.
Where the button appears
The daemon must advertise session_side_task. Without that capability, the entry is absent. It is also absent from split-view, embedded panes and side-task panes; this is not a button available across every CLI or IDE interface.
The explanation follows the UI language. The PR describes English and Simplified Chinese, with Russian falling back to English—not native Japanese or Traditional Chinese support. A generated recommendation remains assistance with a decision, not a guarantee of correctness.
Multiple child questions are a separate change
Another update lets ordinary local files/Shell sessions and built-in depth-1 public children keep independent pending questions. The parent page brings questions and permission requests together, so either child can be answered first. Selections, drafts, submission state and errors are kept separate for each target.
Unsent text lives only in page memory: refreshing does not preserve an unfinished draft reliably, even though durable requests and accepted answers can be restored. A revised request can clear its own older draft. An accepted answer is not the same as resumed execution.
The change does not cover SSH, resident, MCP, Hooks, Team members, workflows, snapshots, extension-defined or deeper children. Existing limits still apply: depth 1, four active children and 64 launches over the lifecycle; waiting children still count. This is not unrestricted concurrency or a global expansion of the details button.
We haven’t installed this release or tried these features.