Get branching back in your Claude chats

Claude’s merged app cannot branch a conversation from an earlier message, so one edit can cost you the reply you liked. This ready-to-paste prompt forks any chat into a new one, plus three other routes that help.

How-to

Anthropic’s help page on the merged app, where chat and Cowork became one Claude, rolling out to Pro and Max first on the web, desktop and phone, lists one current limitation: “Branching a conversation from an earlier point isn’t available.”

Users on r/ClaudeAI also report that editing or retrying a message no longer keeps the < 1/2 > arrows that let you flip to the old version.

First, check your own chat

  1. Edit a message in a chat you do not mind changing. If arrows appear under it to switch versions, your account still has the old branching, and you can carry on as before.
  2. If no arrows appear, copy the reply you want to keep into a note before you edit or retry, because the old version may not come back.

The prompt: fork this conversation

Paste this at the end of the chat you want to branch. It writes an opener for a new chat holding everything up to the message you pick, with each decision marked as yours or Claude’s, and keeps everything up to that message as it is.

PromptFork this conversation
You are my handover editor. I want to branch this conversation: start a new chat that carries everything up to one chosen message, so I can try a different direction while this chat stays as it is. The new chat will see nothing except the opener you write. Anything you leave out is lost, and anything you get wrong or make up will be treated as settled fact, so accuracy matters more than length.

ABOUT THE BRANCH (I fill this in once; any line can say "not stated")
- The message to branch from: [quote the first few words of that message, e.g. "Can you redo the budget with the cheaper venue", or write "the latest message"]
- What the new chat is for: [e.g. "try the same sales pitch for a hospital buyer", "go back to before we chose the three-day itinerary and plan five days", "rewrite chapter 2 in first person"]
- Anything from after that point I still want to keep: [e.g. "nothing", "the pricing table we agreed later", "my note about the client's deadline"]
- Files or attachments in this chat: [e.g. "budget.xlsx and the venue brochure PDF", or "not stated"]
- How long the opener can be: [e.g. "under 400 words", "as long as it needs"]

HOW TO WORK, IN STAGES

Stage 1. Find the branch point. Quote the message I named, word for word, with one line on what was happening at that moment. If you cannot find it, or more than one message matches, stop and ask me which one before doing anything else. If parts of this conversation reach you only as a summary, say which parts, because details from them may be missing.

Stage 2. Gather the state up to that point, and only up to that point:
- The goal: what I am trying to get done, in one or two sentences.
- Decisions made, each with the reason given at the time.
- Facts and constraints I gave you: names, numbers, dates, budgets, audience, rules. Copy them exactly.
- Things tried and dropped, with why, so the new chat does not suggest them again.
- Open questions still unanswered at that point.
- The current version of the work: paste it in full if it is under about 300 words; if longer, give the parts the new direction depends on, word for word, and list what you left out.
- Files: each file's name, what it contains as far as this chat shows, and whether I need to attach it again in the new chat.
- How I asked you to write or format things, if I said.
If something after the branch point changed one of these, leave the later version out unless I listed it under "keep", and put it in the left-behind list in Stage 5.

Stage 3. Mark who decided what. Tag every decision "my decision", "your suggestion I agreed to" or "your suggestion, not confirmed". If you cannot tell, tag it "not clear" and do not upgrade it.

Stage 4. Write the opener. One paste-ready block, written in the first person as me, with short headed sections: Where we are, The goal, Decided so far, Facts to use, Already tried, Open questions, The work so far, Files. End it with the first task for the new chat, taken from what the new chat is for, and this line: "Before you assume anything marked [NEED], ask me." Use "not stated" where this chat never said, and [NEED: what is missing] where the new chat cannot do its first task without it.

Stage 5. Under the block, outside it, give me:
- Left behind: anything from after the branch point you left out, one line each, so I can add it if I want.
- Attach again: the files to upload with the opener.
- Questions: anything you were unsure about.

Never invent a fact, number, name, file or decision to fill a gap. If this chat does not say it, write "not stated".

SELF-CHECK BEFORE YOU ANSWER
- Every fact in the opener appears in this conversation, word for word or clearly the same.
- Nothing from after the branch point is in the opener unless I asked to keep it.
- Every decision carries a tag from Stage 3.
- The opener makes sense to someone who has never seen this chat.
- Any part you only saw as a summary is named in Questions.

What a good opener looks like, for a branch that turns a three-day trip into five:

  • Decided so far: three-day itinerary in Lisbon (my decision); hotel near the river (your suggestion I agreed to).
  • Facts to use: travelling in early December; budget [NEED: total budget].
  • Already tried: a day trip to Porto, dropped because the train took too long.
  • First task: stretch the plan to five days, same hotel. Before you assume anything marked [NEED], ask me.

Run it in four moves

  1. Pick the message to branch from. Scroll to where the chat took the turn you want to undo, and copy its first few words for the set-up.
  2. Fill in the set-up lines, then paste the prompt into the old chat. That chat holds the full history, so Claude can quote it exactly. If Claude says it is summarising earlier messages, run the prompt straight away, before adding more turns.
  3. Fix the gaps. Read the opener, fill in anything marked [NEED], and add any item from the left-behind list you still want.
  4. Start a new chat and paste the opener as your first message. If the old chat lived in a Project, start the new one in the same Project so its files and instructions come with it. Attach the files Claude listed.

You now have two branches: the original, which keeps everything up to that message as it is, and the new chat heading the other way. Repeat it from the same message as often as you like.

Three other ways to branch

A Claude Project for the shared part.

Best for: work you keep branching, such as a client, a book or a job hunt.

How: put the background that never changes in the Project’s files and instructions, and every new chat inside it starts with that already loaded, so the fork prompt only has to carry the latest decisions. Stop re-explaining yourself with a Claude Project sets one up.

Verdict: the best partner for the prompt.

Claude Code’s own branch command.

Best for: anyone already working in Claude Code, which needs a paid plan.

How: the commands reference says /branch creates a branch of the conversation at that point and switches you into it, and the original stays available through /resume.

To branch from an earlier message: /rewind (or Esc twice) opens a list of your prompts; the checkpointing page says Restore conversation rewinds to that message and puts your original prompt in the box to edit and resend.

Verdict: built-in branching that works today, but it lives in Claude Code, so it does not reach your claude.ai chats.

Claude QoL, a community browser extension.

Best for: heavy claude.ai users happy to vet an add-on.

How: Claude QoL by the developer lugia19 adds forking a chat into a new one, with the full content or a summary up to a chosen point, plus chat search across branches. It is free and open source, on Chrome and Firefox, with version 3.2.0 released on 14 October 2026.

Safety check before you install:

  • What it can reach. Its code list gives it storage plus access to claude.ai, and to OpenAI and ElevenLabs for the optional read-aloud and dictation features, which use your own key. If the install screen asks for more than that, stop.
  • What it can read. Access to claude.ai means it can read every chat you open, which is how forking works; its privacy page says it does not handle or store any user data.
  • What it adds to your account. It creates a switched-off skill called qol-encryptionkey-do-not-delete, which holds the key that encrypts the copy of your chats it keeps in your browser.
  • Who made it. One independent developer made it. Leave it off a work account unless your IT team agrees. The desktop version needs a separate launcher app, so start with the browser.

Verdict: the closest thing to the old arrows today, for a personal account.

The honest bit

  • The prompt can only copy what the chat still holds. Anthropic’s context window page says that when a conversation nears its limit, Claude summarises earlier messages, so in a very long chat the early part may reach the prompt as a summary.
  • So test the opener. Check it for two details you remember from the start; if either is missing, paste them in yourself.
  • Check both before you rely on them. Anthropic calls missing branching a current limitation, and the extension changes as claude.ai does. The facts here come from Anthropic’s help pages, the Claude Code docs and the extension’s own pages, read 18 October 2026.

Fork one chat today

Open the long chat you keep scrolling through, find the message where it went somewhere you did not want, and run the prompt from there. You keep the original and get a clean start on the other road.

A few quick questions

Why does Claude keep compacting my conversation?

When a chat nears the limit of what Claude can hold at once, Claude summarises the earlier messages to make room. Anthropic’s context window page says longer conversations that trigger this use more of your usage limit, so a fresh chat started with the fork prompt can also make your plan go further.