Problem
When a question contains a mistake, asking it again leaves the original exchange in the conversation. People need to correct the question without losing useful work.
Solution
Let people edit a sent message and continue from the revised version. Keep the original message and its replies available as a separate version of the conversation.
Show a clear version control on the edited message so people can return to the earlier exchange. Explain what will happen to later replies before the edit is sent.
Open the editor with the original text and attachments intact. Let people cancel without sending, and make clear which version of the conversation the assistant will use next.
Use when
People can correct an earlier question and need to keep the conversation that followed it.
Don’t use when
The turn triggered a side effect. Once a message has sent an email, filed a ticket or written to a system of record, editing it rewrites a history that no longer matches the world, and an append-only correction is the honest shape.
Trade-offs
Keeping alternate conversations prevents data loss but makes navigation more complex. People can lose track of which version they are reading. An edited conversation also needs its original messages preserved if it serves as a record of what happened.
Checklist
- What happens to the turns after the edited one?
- Is the previous version still reachable, and is that visible without hovering?
- Does the viewer learn what will be discarded before they commit?
- Does the edit box open pre-filled with the cursor at the end?
- Does Escape abandon the edit cleanly?
- Are attachments from the original turn carried over?
- Can the viewer tell which branch they are currently on?
- What does an export or a shared link contain when branches exist?
- Is the control available on the keyboard?
- Is editing blocked on turns that caused a side effect?
Compare
ChatGPT puts an edit control on the user turn and pages between versions, so the branch is preserved and presented as a small counter rather than a visible tree. Claude offers the same in-place edit and pairs it with model switching at the retry, so a correction can change the question and the answerer at once. Perplexity treats a revised question closer to a new search than an edit of the thread, which suits a product where each answer is largely independent. Slack cannot offer the pattern at all in the same form, since an AI exchange lives in a channel where editing a message rewrites a shared record other people have already read.
Related
Regenerate requests another answer without changing the question. Message turn holds the edit control, and Composer provides the editing field.
Conversation history must preserve alternate versions. Context meter reflects the messages included in the active conversation.