AI Handoff

AI Handoff is the controlled side of AI orchestration: it sends the right work context into Cursor, Claude, Codex, a terminal workflow, or an agent.

What gets handed off

The launcher builds the prompt from the work item, linked documents, comments, and details.

Good handoff starts before launch. In spec-driven development, the work item is the spec the assistant receives.

Send to app

From a work detail page, Send to app lets you choose the tool that should receive the context. Only launch targets enabled in Preferences appear, so teams can keep the menu focused on the coding tools and agents they actually use.

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 also move it to In Progress in the same action. Completed work uses review-style handoff.

Launch modes

Launch modes decide whether the target tool should plan, build, review, or fix the work. The exact mode behavior lives in Send to app.

Trust boundary

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

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

If a target tool does not appear, configure launch targets in Send to app. Terminal handoffs belong in Use in Terminal. Queued Codex work belongs in Local Workers, with lifecycle details in Agent Sessions.