Fork
Forking in AI chat means branching the conversation or task at a decision point—creating a new path without losing the original thread.
It differs from regenerate: fork preserves both explorations so users can compare directions instead of replacing one answer with another.
What it means
The product copies context up to a message or step into a new thread/session, letting users pursue alternate prompts, edits, or agent plans in parallel.
Why designers should care
Fork UX needs visible branch points, labels (“Accessibility pass”, “Option B”), and easy return to the parent thread—especially for design critique and spec exploration.
Example
ChatGPT’s “Branch in new chat” after editing an earlier message keeps the original thread intact while the fork explores a new tone; both remain in history.
Common mistakes
- • Fork buried three menus deep with no discoverability.
- • Forking that silently drops attachments or tool context from the parent.
- • No way to compare or merge insights back from a fork to the main thread.