Cross-app handoff
Passing an artifact to the tool it wants to live in.
A brilliant draft that's trapped in a chat window is a draft that dies. The handoff pattern is the gesture that lets the output leave without losing its state — to Docs, to Figma, to a PR, to a Linear ticket, to wherever the work actually continues.
Every AI product with real use eventually runs into the same limit: the chat window is a launchpad, not a landing pad. The products that graduate past that limit do it through handoff.
"Chat is a launchpad, not a landing pad."
Name the destination, show the payload, send.
A good handoff card has three elements. It names the destination, specifically — not "Send to Docs" but "Append as a new section of Q3 Plan · Draft." It previews what will actually be sent, so the user sees the wording they'd see on the other side. And it sends with one click, with a 10-second undo that lives where the user can actually find it.
A pinned row of recent destinations sits above the card. Most handoffs go to the same few places; the product should learn them and save the user the hunt.
- · Cut the four-step wizard to two.
- · Replace the video with an interactive composer.
- · Move the sample data picker to after the first prompt.
Append as a new section: Onboarding, shorter. Cut the four-step wizard to two. Replace the video with an interactive composer. Move the sample data picker to after the first prompt.
Chat is the launchpad. The destination decides where the work continues.
The second location is where work happens.
The chat window is not where most work lives. It's where work starts. PMs write specs in Docs. Designers iterate in Figma. Engineers review in a PR. A product that insists the work stays in chat is fighting the user's existing habits, and losing.
Handoff is the pattern that respects the user's existing workflow. It's also, quietly, what turns an AI product from a demo into a piece of infrastructure.
The handoff I'd ship.
- Named destinations, not generic ones. "Send to Docs" is a lookup-in- progress. "Append to Q3 Plan · Draft" is a commitment the user can verify at a glance.
- Preview is the payload. The card must show exactly what the other app will receive, not a summary of it. If the artifact is longer than a few lines, show the first and last lines plus a count of what's between.
- Undo, don't confirm. A "Send?" dialog kills every handoff. A ghost toast with an undo for 10 seconds keeps the user in flow and recoverable.
Drift between artifact and sent copy.
The sneakiest failure of this pattern is that the thing the user sees in chat is slightly different from what lands in the destination. Formatting is lost. A callout becomes a paragraph. A bullet list becomes prose. The user discovers this only when their collaborator opens the doc.
Preview is the truth. If the destination can't render the artifact faithfully, say so on the card before the send, not after.
What this pattern gets wrong when it gets wrong.
- Artifact drift
- An artifact that edits itself across turns without a clear trail, so the user can't reconstruct how it got to its current state.
- Consent skip
- Capturing, transmitting, or acting on input the user didn't agree to share in this moment.
- Modality mismatch
- The product answers in one modality when another was implied, or mixes modalities in a way the user can't combine.
Three shipping variants worth copying.
- A handoff card that shows the destination app, the doc name, and a preview
- A 'revert the send' ghost toast that lasts 10s
- A pinned recent-destinations row so the next send is one tap