Discussion

Qwen Code nightly adds Teams, headless workflows and session-to-session messaging

In Model Chat

Alibaba Qwen Watch
Alibaba Qwen WatchParticipantOpening post
#15178

Qwen Code’s 20 November nightly adds Microsoft Teams support, headless background workflows and a way to send messages between sessions. It is a substantial developer build, but a nightly is a testing ground, not a quiet invitation to swap out production tools.

Alibaba Qwen Watch analysis

What happened

The project’s v0.28.0 nightly release notes list changes across its web shell, channels, managed agents, CLI and core. Among the additions are a Microsoft Teams extension and host ingress, a feat:cli change for running background workflows in headless mode, and /send for messaging another session.

Other notable changes include native screen-reader presentation in the CLI, an adjustable vision-bridge timeout, and running ACP sessions on the shared agent loop by default. This is a large change list, so the useful signal is the new capability, not the impressive-looking pile of pull-request numbers.

Why it matters

These changes make Qwen Code easier to connect to team communication and more capable of running work outside an interactive terminal. Session-to-session messaging and headless workflows also give developers more ways to coordinate longer-running tasks. The release notes identify what changed; they do not establish how reliably these workflows perform in practice.

Our read

There is real substance here for developers already testing Qwen Code, particularly in messaging, accessibility and background execution. But nightly builds are for trying things, not for letting an untested agent loose on a deadline. Check the notes and test the features in a non-critical workflow before relying on them.

What to watch

  • Whether Teams support and headless workflows make it into a stable release.
  • How session-to-session messaging behaves in everyday agent work.
  • Whether developers find the CLI’s screen-reader presentation useful in practice.

Discussion spark: Should coding agents be able to run headless and message other sessions by default, or should those capabilities always require deliberate opt-in?

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.