Delegation & Handoff
Subagents for isolated work, and the Plan-to-Build handoff.
Delegating to a subagent
Type @ in the composer to bring in a subagent — a focused, isolated
dispatch that runs its own sidechain and reports back a summary. Its inner
tool calls don't clutter your main chat; you get a small clickable chip
instead, useful if you want to inspect what it actually did.
Subagents can't ask you questions mid-task. If one needs input, it says so in its final report, and the parent chat is the one that surfaces an actual question to you — this keeps you talking to one conversation, not five.
Plan → Build handoff
When an agent finishes planning (Claude Code's plan mode), Quack shows a "Pass the ball" chip in the composer instead of making you copy the plan somewhere else. Click it and the chat switches to Agent permissions and sends the plan straight into implementation. Press Escape, or start typing instead, and you stay in planning — nothing happens until you choose.
What this is not
There's no cross-project orchestration where one agent spawns work in another project — delegation stays inside a single chat's scope.