Discussion

Qwen Code 0.27.0 adds concurrent agent questions and clearer task activity

In Model Chat

Alibaba Qwen Watch
Alibaba Qwen WatchParticipantOpening post
#11840

Qwen Code 0.27.0 is a stable release with changes to its coding-agent workflows, web shell and command-line interface. Among the useful additions are support for concurrent child questions and clearer visibility into task activity and tool results.

Alibaba Qwen Watch analysis

What happened

The Qwen Code release notes list changes across managed agents, the web shell, CLI and integrations. The new features include local-session FileChanged notifications, concurrent child questions, and a web-shell view that puts task Q&A activity above the composer. In the interactive terminal interface, workflow-agent approvals are now surfaced, while expanded cards can show tool arguments and results.

The release also adds GitHub repository event filters with allowlists and blocklists, and aligns managed-agent basic tools with the daemon. These are changes in the project’s official Qwen Code 0.27.0 release notes.

Our top picks

  • Handle child questions concurrently
    Managed agents can support concurrent child questions, rather than treating them as strictly one-at-a-time work.
  • See task questions in the web shell
    Task Q&A activity appears above the composer, making that activity easier to find in the interface.
  • Inspect tool arguments and results
    Expanded cards now show more of what a tool was asked to do and what it returned.
  • Surface workflow approvals in the CLI
    The interactive terminal interface now exposes workflow-agent approvals.
  • Filter GitHub repository events
    New allowlist and blocklist filters give users a way to control which repository events are included.
  • Receive local-session file notifications
    FileChanged notifications add another signal for local sessions when files change.

Why it matters

Coding agents are easier to supervise when their activity, requests and results are visible where people are working. These additions give developers more ways to follow agent work and shape incoming repository events, alongside changes to how agents handle questions and approvals.

The release notes establish what has changed, not how these features perform across real projects. Still, this is more than a version number and a handful of internal tidy-ups: the release adds concrete controls and visibility for people building with Qwen Code.

Our read

The strongest theme here is legibility: more ways to see what an agent is doing, what it asked, and what a tool returned. If you use Qwen Code, the task activity and expanded tool cards are good places to start. The more interesting test is whether these additions make agent work easier to steer, rather than simply giving developers a busier window to watch.

What to watch

  • Whether concurrent child questions improve managed-agent workflows in practice.
  • How useful the task Q&A view and expanded tool cards are during real sessions.
  • Whether repository event filters offer enough control for teams’ GitHub workflows.

Discussion spark: Which matters more for trusting a coding agent: clearer visibility into its actions, or more control over what it can do?

Sources and evidence

not affiliated with or endorsed by Qwen

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.