Problem
An answer is unhelpful, but the person cannot identify a specific correction. They need a way to request another attempt without retyping the question.
Solution
Offer another response to the same request while keeping the earlier answer available. Use clear version controls so people can compare attempts and choose which one to continue from.
Explain that another attempt may differ without being better. Where useful, let people add direction, such as asking for a shorter answer, or choose a different model.
Make any additional usage cost clear. Preserve the selected response and its follow-up conversation when people return later.
Use when
Another attempt can produce a useful alternative, and people can judge which result meets their needs.
Don’t use when
The task has a right answer the model either reached or didn’t. Rerolling an arithmetic error or a factual lookup is superstition, and offering the control there teaches a bad habit. Also avoid it where a response has already caused a side effect, since the second answer can’t undo the first one’s consequences.
Trade-offs
Repeated attempts consume time and usage without fixing an unclear question. Keeping alternatives prevents loss but complicates the conversation history. Version controls must be visible enough for people to find earlier answers.
Checklist
- Does the previous response survive, and can the viewer get back to it?
- Is the count of alternates visible without hovering?
- Can the viewer give the retry a direction rather than rerolling blind?
- What happens to turns that came after the one being regenerated?
- Does the model know it is being asked again, or does it see an identical fresh request?
- Is a retry recorded as a quality signal anywhere?
- Does each regeneration bill, and does the viewer know that?
- Is the control offered on tasks where rerolling cannot help?
- Can the viewer compare two alternates side by side, or only one at a time?
- When the conversation is shared or exported, which alternate goes with it?
Compare
ChatGPT keeps earlier attempts on the turn behind a small pager, so the transcript stays linear while the branch is preserved underneath it. Gemini has historically gone the other way and surfaced multiple drafts as a first-class thing to look at rather than something to page through, which treats variation as information instead of an accident. Claude attaches retry to the response and lets the model be switched at the same time, so the second attempt is a different question rather than the same one asked twice. Perplexity frames the rerun around the source set rather than the prose, so trying again is closer to searching again than to rewriting.
Related
Stop generation interrupts an answer in progress. Response actions holds the retry control. Edit and resend changes the question itself.
Model picker can change the model for another attempt. Usage meter shows the cost of retries.