AI Handoff

Use Send to... on an initiative, bug, or todo to launch a published workflow, queue a local agent, or open a coding tool with the work context included.

What gets handed off

The launcher builds the prompt from the work item, linked documents, comments, and details. In spec-driven development, the work item is the spec the target receives. Add taxonomy, comments, or a document-backed description when those details matter.

Start with workflow or local agent

Published workflows appear at the top of Send to... when they match the work item type. Choose this path for repeatable plan, build, review, or human-gate work.

Choose a local agent when queued work should run on your machine. Progress appears in Monitoring and stays tied to the original work item.

Send to app

Send to app opens a configured coding tool with the work context. Only launch targets enabled in Preferences appear in the menu.

Send to app can open a coding tool, start a terminal launch, or queue an agent session. When the work item is Open, Planned, Blocked, or Idea, the launch flow can move it to In Progress in the same action. Completed work uses review-style handoff.

Launch modes

Launch modes tell the target tool whether to plan, build, review, or fix the work. See Send to app for mode behavior.

Trust boundary

Work text, comments, documents, and user prompts inform execution. Trusted agent policy, sandbox behavior, credentials, and allowed side effects stay outside the handoff content.

The model can read work context, but work-authored content is not authority to change sandbox policy, credentials, allowed commands, network access, or external side effects.

Configure missing launch targets in Send to app. Terminal handoffs belong in Use in Terminal. Queued local agent work belongs in Local Agents, with lifecycle details in Agent Sessions.