Working with multiple chats in Build
Why Build lets one flow have multiple chats — separate conversations on the same flow, branches that isolate work until merged, parallel companion builds, the onboarding chat, and read-only sessions from a connected AI tool.
In Build, a single flow can have multiple chats. Every chat builds the same flow — they share one file tree — but each is its own conversation, and some run on their own branch so work stays isolated until it's merged. This lets you organize different pieces of work, build things in parallel, and bring in outside AI tools without losing track of what changed.
Where your chats live
The chat rail on the left of the workspace lists the Chats for the current flow. Select New chat to start another, and use a chat's actions to rename or delete it. Each chat shows its status — for example Generating…, Needs your input, or Last run errored.
Starting a new chat
When you create a chat, Build opens a "Start something" screen: pick a starting point — such as Add a screen or Add an extension — or just start typing your own request.
Branches: work without disturbing the main build
A chat can work on its own branch — its edits land on a separate line of history instead of the flow's main file tree, and merge back into the main build when the work is done. This is what lets you try a change or build a feature in one chat without affecting what's already working in another.
Companion builds run in parallel
When a build includes a self-contained add-on — something that touches its own files, like a print receipt or a standalone extra screen or extension — Build can split it off as a companion that builds in parallel on its own branch and merges back automatically when it's finished. If a companion's edits overlap another change to the same files, Build flags a conflict for you to review before merging, so nothing is overwritten silently.
The onboarding chat
Alongside a fresh build, Build may add a separate onboarding chat — a guided concierge that helps import your website, brand, and design, and get your store set up. It's its own chat in the rail and doesn't use your build model.
Chats from your own AI tool (MCP)
If you connect your own AI tool — Claude Code, Cursor, or ChatGPT — over MCP, its work shows up as its own chat, labelled "Built over MCP — read-only session." It updates live as the tool works, and you can continue it in a new chat to pick up the work directly in Build.
Do my chats share the same flow?
Yes. All chats operate on the same flow's files. Chats working on a branch keep their edits isolated until they merge, and every change is saved as a restorable checkpoint — so you can always roll back if something isn't right.
Frequently asked questions
How do I start a new chat?
In the chat rail on the left, select New chat. The "Start something" screen lets you pick a starting point — like Add a screen or Add an extension — or just start typing.
Do multiple chats create separate flows?
No. Every chat operates on the same flow and its shared files. A chat may work on its own branch, but that work merges back into the one flow.
What is a read-only chat?
It's a session driven by a connected AI tool (Claude Code, Cursor, ChatGPT) over MCP. It's labelled "Built over MCP — read-only session" and updates live as the tool works; you can continue it in a new chat to take over in Build.
What happens if two chats change the same files?
Companion builds run on their own branch and merge back automatically. If their edits overlap another change, Build flags a conflict for you to review before merging.
Can I rename or delete a chat?
Yes. Use the chat actions in the rail to rename or delete a chat.