Who it is forAn agent engineer or product designer building a phone automation agent who needs concrete examples of how a planner handles multi-step tasks.
The problemDesign discussions about planner behavior stay abstract until you see actual tool arguments, returns, and failed attempts.
The outcomeA short list of observed patterns, such as confirming prerequisites, passing artifacts between sub-agents, and correcting after errors, each tied to a specific replay.
What you need first
- A web browser to open the project website and the arXiv page
- A BibTeX file or reference manager if you plan to cite the paper
Steps
- Open the interactive examples on the project website at https://tongyi-mai.github.io/Qwen-Planner-Agent/#demos.
- Open the Sub-Agent Coordination example and note when the planner waits for confirmed downloads before handing off filenames.
- Open the Error Recovery example and record the failed conversion, the alternative tool call, and the final message.
- Write down each pattern with its replay name so your design notes can cite it.
Prompt for your agent
Using the Tongyi-MAI/Qwen-Planner-Agent project website demos, review the Error Recovery and Sub-Agent Coordination replays and write a summary of <design question> with one bullet per observed behavior. Expected output: a bulleted list where each bullet names the replay and the tool result that triggered the behavior. Verify that every bullet cites a replay that exists on the demos page.
Caveat. The replays show recorded runs on the authors' setup, and the repo does not provide the agent code to rerun them.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Tongyi-MAI/Qwen-Planner-Agent and "Review recorded planner tool-use traces for agent design"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer