Interrupt and Resume
Interrupt and resume is an AI UX pattern that lets users stop generation or speech mid-turn and continue later with preserved context, what was said, what was cancelled, and where to pick up. It keeps conversations recoverable instead of forcing a full restart.
When to use
Critical for voice assistants, long-form chat responses, and agentic chats where users need to redirect the model quickly without resetting the entire thread.
When not to use
- Atomic transactions that cannot partially complete (prefer full cancel + undo).
- Tiny answers that finish before an interrupt control is usable.
- Batch jobs better served by pause/checkpoint than conversational interrupt.
Anti-patterns
- Stop that discards the partial answer with no way to keep or edit it.
- Resume that invents continuity the model no longer has in context.
- No visible interrupted state. UI looks idle while a job still runs.
- Voice interrupt that leaves the mic hot without a clear listening indicator.
How products use it
| Product | Implementation |
|---|---|
| ChatGPT | Stop generating; edit or regenerate; voice mode barge-in. |
| Claude | Interrupt streaming replies and retry or continue the thread. |
| Voice assistants (Siri / Google / Alexa) | Barge-in to halt speech and issue a new or continued request. |
| Coding agents | Cancel a run and resume from a checkpoint or revised instruction. |
Use this pattern in your project
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Interrupt and Resume" AI interface design pattern.
Pattern Definition:Reading Q2_report.pdf
RunningYou can pause without losing progress.
Frequently asked questions
What is interrupt and resume in AI UX?
It is the ability to stop an AI response or action mid-stream and continue later with clear state, keeping partial output and context instead of forcing a brand-new session.
How is it different from regeneration?
Regeneration replaces an answer with a new one. Interrupt stops the current run; resume continues or redirects from that point with memory of what already happened.
Should partial text be kept on stop?
Usually yes, mark it incomplete and let users copy, edit, or ask to continue. Deleting on stop punishes users for correcting course early.
What does good resume need?
A preserved transcript, explicit “continued from interrupt” cue, and any tool side effects already applied called out so users do not double-run them.
Related patterns
- Chatbot
Chat Artifacts
Open generated docs and code in a side panel
- Chatbot
Thread Branching
Edit and fork chats
- Chatbot
Regeneration Carousel
Swipe bot responses
- Chatbot
Response Refinement
Modify AI responses with contextual actions
- Chatbot
Conversation History Search
Search through past conversations
- Chatbot
Message Pinning
Pin important messages