Analysis & perspective
Qwen Intelligence: a three-agent phone stack, hands-on with the planner — and no weights
Alibaba's Qwen Intelligence is a direct answer to Apple Intelligence, aimed at phone makers rather than at you — Honor is the first partner. It is worth knowing about now because this is the shape agent capability will arrive in on Android handsets, and because the planner is free to try today in their console.
"Qwen Intelligence is Here: Mobile AI Agents" by Fahd Mirza — Watch on YouTube →
The three agents
- Planner — breaks a goal into ordered steps.
- Use agent — actually operates the apps.
- Creative agent — generates images.
The planner is the piece you can get at directly: create a free account in their console, add a planner agent, and you land in a debug panel where you set a one-line system role and give it a task.
The hands-on result
The test prompt was deliberately two-part — set an alarm for 7am and text my wife I'll be late — with no phone number or contact configured. The planner returned a clean step-by-step instruction set with recipient and message text broken out, plus a final confirmation step. It runs on a Qwen 3.8 model behind the scenes, and the output can be driven from any voice assistant.
The planner decomposing a two-part instruction correctly, with a confirmation gate at the end, is the part worth noting — a confirmation step before acting is the right default for an agent operating a phone.
The published examples, which are the real signal
Alibaba's own examples describe behaviours that are genuinely hard, and they are the best available evidence of what the stack does:
- Memory-guided planning — told to run a saved dev workflow, the agent searches memory, recovers the full procedure, then opens the editor and enables USB debugging in the right order.
- Trusting the tool over its own earlier answer — a tool error contradicted a previous reply, and the agent went with the tool result rather than defending itself.
- Sub-agent coordination — waits until downloads are confirmed, then hands exact filenames to the file manager to sort.
- Targeted state correction — compares accessibility settings against a saved routine and fixes only the mismatch, leaving everything else alone.
- Error recovery — after two unit-conversion failures it switched to the calculator instead of retrying the same route.
The caveats, stated plainly
The scores come from Alibaba's own MobilePA-Bench. Their 27B planner is reported at 77.1 overall, just ahead of GPT-6 Astra at 76.8 on that chart, and ahead of Claude Opus 5 and Fable 5 at much lower output cost. These are the vendor's numbers on the vendor's benchmark — the video says so explicitly, and so do we. Our aggregated leaderboard marks vendor-run results as such for exactly this reason.
The other caveat: the repository is a blog and report site — no weights and no code have been released. Despite the Qwen name's association with open weights, this one is closed, which as the video notes makes it "just like Apple Intelligence where everything is a black box."
Key Takeaways
- Three-agent split — planner, app operator, creative — is becoming the standard shape for on-device assistants.
- The planner is free to try in the console today; the rest ships through phone makers, starting with Honor.
- A confirmation step before acting is built into the planner's output. Copy that pattern.
- Treat the 77.1 figure as a vendor claim on a vendor benchmark, not an independent result.
- No weights, no code — the Qwen branding does not mean open here.
How we treat vendor-run numbers: the benchmarks leaderboard. Where mobile agents fit alongside the desktop platforms: the comparison guide.





