Overview
How might we treat alternate answers as siblings people can compare instead of overwriting the last draft?
When variation helps people choose
- Gemini, ChatGPT, and Claude where Regenerate produces a different take on the same prompt.
- Creative, marketing, and drafting flows where comparing two or three variants beats editing one bad answer.
- Surfaces where retry should keep prior drafts reachable with prev/next, not delete them.
- Products that cap stored variants (three to five) so the carousel stays scannable.
When one audited answer is required
- Deterministic tools where every run should produce the same result.
- High-stakes answers that need a single audited response, not a pile of variants.
- Streaming-only surfaces with no room to store or navigate prior generations.
States
Design variant storage and navigation, not only a Regenerate button.
Original
The first answer is visible. Regenerate is available when a different take might help.
Regenerating
A new variant streams or loads. Prior drafts stay stored; the UI does not wipe the current answer.
Stored
Multiple full answers exist for one prompt. A counter shows which variant is active.
Browsing
Prev/next or dots flip between siblings. Content swaps in place; the prompt stays fixed.
Selected
The person settles on one variant. Copy, share, and follow-ups use the visible draft.
Discarded
Weak variants can be removed. The cap prevents endless piles of unread alternates.
Key UX elements
The parts that must be present for variants to feel comparable, not disposable.
Add a sibling, do not replace silently.
Regenerate should append a new full answer. Overwriting the prior draft with no undo breaks trust.
Show which draft is on screen.
A 2 of 3 counter or dot row makes the active variant obvious at a glance.
Offer prev/next beside the answer.
Arrows or swipe should sit on the response block, not buried in a overflow menu.
Limit how many variants you keep.
Three to five stored answers is usually enough. Drop or merge weak ones so the carousel stays readable.
Make the visible draft the working copy.
Copy, export, and thread continuation should follow the variant on screen, not always the first.
Carry retry reason into the next variant.
Thumbs down or “try again” should inform regeneration instead of producing a random reroll.
Anti-patterns to avoid
Regenerate that overwrites the previous answer with no undo.
Carousels that hide which variant is currently selected.
Keeping infinite variants until the UI becomes unreadable.
Regenerating without preserving feedback that caused the retry.
How products use it
| Product | Implementation |
|---|---|
| Gemini | Response carousel controls to flip between regenerated answers. |
| ChatGPT | Regenerate with access to prior variants in the same turn. |
| Claude | Retry responses while keeping earlier drafts reachable. |
| Jasper | Multiple generation variants for marketing copy selection. |
Implementation
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 "Regeneration Carousel" AI interface design pattern.
Pattern Definition:Frequently asked questions
What is a regeneration carousel?
A regeneration carousel keeps several AI answers to one prompt and lets the user move between them with arrows, dots, or swipe, instead of deleting prior drafts.
How many variants should you keep?
Three to five is usually enough. Cap storage and let users discard weak ones so the carousel stays scannable.
How does this differ from response refinement?
A carousel stores full alternate answers. Refinement edits the current answer with shorten, expand, or tone actions without creating a full sibling draft.
Should regenerate interrupt streaming?
Yes. Cancel the in-flight stream, then start a new generation. Show which variant index is active when the new answer lands.