How to merge a branch back

Merging carries the useful part of a branch somewhere it can keep living. Plan note first: the Free plan includes 3 merges a month, and Pro and Team lift that to unlimited.

You can start a merge from three places:

1. Highlight text in a reply, then click "Merge" in the tooltip that appears.
2. Click the "Merge" button on any message.
3. Click the "Merge" button in the pane header.

All three drop you into the same staged flow:

1. Select the content to carry over: the AI summary, individual messages, or both. Click Continue.
2. Choose the target. There are four: back into the parent branch, into another branch, into an existing document, or a new document created from the merge.
3. Choose the strategy. AI-Assisted synthesizes the content and understands the surrounding context, and it's the recommended choice for most merges. Replace swaps the message. Append adds the content to the end. Insert places it at the branch point.
4. Click "Preview Merge". You get a side-by-side diff of what the merge will do: red for removed, green for added. The preview is a dry run.
5. If it looks right, click "Confirm Merge", which is what actually applies it. If it doesn't, step back and change the strategy; the preview exists precisely to catch a Replace that should have been an Append.

Two pieces of advice from our own use.

When in doubt, AI-Assisted. The three mechanical strategies do exactly what they say with zero judgment, which is what you want only when you already know precisely where the content belongs. For "take the good parts of this branch and work them in properly", AI-Assisted is the one doing actual synthesis.

And don't overlook the document targets. A merge doesn't have to land in a branch at all. Sending the result into an existing document, or creating a new document straight from the merge, is how a finished exploration turns into an artifact instead of staying a chat you'll have to dig up later.

If you're trying to combine several branches at once, message-by-message merging gets tedious fast. That's the Merge Board's job: a full-page surface built for multi-branch synthesis.