---
title: "Alibaba's Qwen-Audio-Agent Hits 91% Success Splitting Voice Tasks Between Two AI Contexts"
subtitle: "Alibaba's Qwen team splits a voice assistant into a fast talker and a slow thinker, hitting 91% task success on a cockpit benchmark."
url: "https://alphasignal.ai/news/alibaba-s-qwen-audio-agent-hits-91-success-splitting-voice-tasks-between-two-ai"
author: "AlphaSignal Newsroom"
author_url: "https://alphasignal.ai/editorial-team"
company: "AlphaSignal"
company_url: "https://alphasignal.ai/company/alphasignal"
published: "2026-09-21T17:40:55.000Z"
updated: "2026-09-26T01:56:11.681Z"
type: "Paper"
topics:
  - "Agents"
  - "Audio"
subtopics:
  - "Computer Use"
  - "Tool Use"
  - "Realtime Voice"
upvotes: 11
source_url: "https://arxiv.org/abs/2609.25195"
comments: 0
truncated: true
---

# Alibaba's Qwen-Audio-Agent Hits 91% Success Splitting Voice Tasks Between Two AI Contexts

> Alibaba's Qwen team splits a voice assistant into a fast talker and a slow thinker, hitting 91% task success on a cockpit benchmark.

# Qwen Splits Voice-Agent Work Between Live Dialogue and Background Tasks

Alibaba’s Qwen team has described Qwen-Audio-Agent, an architecture that keeps a voice conversation running while longer tasks execute in a separate model context. An orchestration runtime routes quick actions to the foreground model and delegates multi-step work to a background agent.

The [technical report](https://arxiv.org/abs/2609.25195) says mixed routing achieved 91.04% task success on a 134-case in-house cockpit benchmark. It also recorded lower latency on matched successful turns than configurations that routed every tool call through the foreground or background model.

## One Conversation, Two Contexts

Speech-native models can stream dialogue and call tools, but complex workflows often consume conversational context and delay the next spoken turn. A request to plan a multi-stop route, reserve a table, and notify a passenger may require several tool calls, confirmations, retries, and state updates.

Qwen-Audio-Agent assigns those responsibilities across four components:

__Core components in the Qwen-Audio-Agent architecture__
| Component             | Responsibilities                                                                                              |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| Frontend Agent        | Processes live audio, manages dialogue, handles direct tool calls, and decides when to delegate.              |
| Backend Agent         | Executes delegated, multi-step tasks in a separate context and returns structured results.                    |
| Orchestration Runtime | Tracks task state, coordinates authorization and user input, processes events, and schedules result delivery. |
| Client adapters       | Supply visual, application, and device state while reporting whether requested actions succeeded.             |

The frontend supports full-duplex interaction, meaning it can receive speech while generating audio. Separating the backend context also keeps long tool traces from filling the conversation history used for immediate responses.

## The Runtime Protects In-Flight Work

The orchestration runtime maintains each task’s lifecycle while the frontend continues the conversation. It records pending work, routes requests for missing information, obtains authorization for sensitive actions, and holds completed results until the dialogue can accommodate them.

_Preview only. Full text requires an AlphaSignal Pro account._

## Sources

- [Qwen-Audio-Agent Technical Report](https://arxiv.org/abs/2609.25195)
- [Qwen-Audio-Agent (HTML)](https://arxiv.org/html/2609.25195)
- [Qwen2-Audio Technical Report](https://arxiv.org/abs/2407.10759)
- [Qwen3-Omni Technical Report](https://arxiv.org/pdf/2509.17765)