How to Use ChatGPT's Branch in New Chat
Branching a ChatGPT conversation starts a new chat from any earlier point in the exchange, leaving the original intact. Here is how branching works, what context carries forward, and how to keep the chosen direction recorded so future sessions start from the right place.
Updated 5 min read
Branching in ChatGPT lets you start a new conversation from any earlier point in an existing one. The original chat stays unchanged, and the branch becomes its own separate conversation where you can take the work in a different direction.
This is useful when a conversation has gone in several directions and you want to explore one specific path without losing the others. The challenge is that branches can multiply quickly and leave no record of which direction was chosen and why. Tools like fenbs solve that by keeping the agreed project direction in a record every connected assistant reads.
How to create a branch in ChatGPT
Hover over any message in a conversation — either one you sent or a response ChatGPT gave. A small set of icons appears next to the message. Look for the option to edit the message or branch from that point.
When you edit a message you sent, ChatGPT generates a new response. The original message and its response are preserved in the same conversation, and a navigation control lets you move between the original and the edited version. If you use "Branch in new chat," the conversation up to that point opens as a fresh chat, leaving the original untouched.
The branch inherits the conversation history up to the point you chose. ChatGPT can refer back to earlier messages in the branch. It does not inherit your Projects context, custom instructions changes you made after that point, or any memory updates written in the original after the branch.
When branching is useful
Branching is most useful when a conversation has produced two or more plausible approaches and you want to test one without overwriting what was already working. Say a design discussion produced three layout options: you can branch from the point where each option was proposed and develop each one without the responses contaminating each other.
It is also useful when you realize partway through a conversation that an earlier message contained a wrong assumption. Instead of continuing with a flawed premise, you branch from before that message and restart with the corrected information.
For related conversation navigation features, the guide on how to archive ChatGPT chats covers hiding conversations you no longer need active, and how to organize ChatGPT chats covers keeping the sidebar manageable as branch counts grow.
What does not carry forward into a branch
A branch carries the conversation history up to the chosen point. It does not carry project-level context from ChatGPT Projects unless that context was established before the branch point. Memory that was saved to your account after the branch point is available in the branch because account memory is global, not tied to individual conversations.
The branch does not carry the reasoning or conclusions from the original chat after the branch point. If you branched at message 10 of a 20-message conversation, messages 11 through 20 in the original are not visible in the branch. If those conclusions were important, copy them into the first message of the branch so they are available from the start.
The problem branches create for project continuity
Branches multiply fast. After a productive session you might have three or four chat variants exploring different directions. The original, a branch from message 8, another from message 12. When you return the next day, or when a colleague picks up the work, it is not obvious which branch represents the agreed direction.
The answer to "which branch are we using?" does not live in ChatGPT. It lives wherever you recorded the decision. If you did not record it, the next session may start from the wrong branch or have to re-read all of them.
This is the same problem that appears with ChatGPT temporary chats and with very long conversations: the actual agreed work gets buried or split across sessions. The ChatGPT project memory guide explores how Projects help; for work that crosses AI apps or involves more than one person, a separate project record is the more reliable solution.
Record which branch won and why
When you branch a conversation and choose a direction, write that decision in fenbs as a Decision: what was chosen, what was ruled out, and why. The next assistant reads that before it starts, so it opens the right branch and continues from the confirmed direction rather than guessing between conversations. Create a free account, add the project and record the first decision.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account and add the project whose direction you are working out in ChatGPT.
- After branching and testing a direction, record the chosen approach in Decisions and rules: write what was chosen, what was ruled out, and the reason.
- Add the key tasks or next steps that came out of the chosen branch as board tasks, so the project's next state is visible outside the chat.
- Connect your AI app at Integrations so the next assistant reads the project context — including the recorded decision — before it starts, not a branch you have to navigate to.
- Link the original ChatGPT conversation or the winning branch in fenbs's Links and listings if you want to be able to find it later.
For questions about exporting the content of a conversation branch, see how to export ChatGPT chats. For managing many conversations across a project, how to organize ChatGPT chats covers naming and grouping strategies that help before the branch count grows.