# A merged branch keeps its history

By Steven Van · 2026-10-07

The editor keeps merged chats read-only, with a status footer linking back to main or an active branch.

After a merge, a branch’s conversation remains readable in the [Base44](<https://creatorstoolbox.com/tools/base44>) app editor. The chat becomes read-only, preserving the discussion that led to the merged changes.

## Finding your way back

A footer explains the branch’s state and links back to main or to a branch still in progress. To revisit a merged conversation, open the branch menu at the top of the chat panel and select the branch. Its status icon identifies it as merged.

## Reviewing saved versions

The merged branch’s version history also stays readable. Restoring a version is available while a branch is still active, and changes only that branch. The [branch documentation](<https://docs.base44.com/Building-your-app/working-with-branches>) explains how to switch branches and review their history.

[![](<https://docs.base44.com/images/base44-docs-og.png>)](<https://docs.base44.com/Building-your-app/working-with-branches>)

![Base44](<https://www.google.com/s2/favicons?domain=base44.com&sz=128>)

Base44

AI app builder — describe what you want and get a fully functional web app in seconds, no coding required.

[View Base44 →](<https://creatorstoolbox.com/tools/base44>)

[Original source](<https://docs.base44.com/changelog/product#october-7-2026>)

[Read A merged branch keeps its history on Creators Toolbox](<https://creatorstoolbox.com/blog/base44-a-merged-branch-keeps-its-history>)

---
Canonical source: https://creatorstoolbox.com/blog/base44-a-merged-branch-keeps-its-history