The short answer
Fork chat means copying a conversation into a new chat so you can take it in a different direction while the original stays exactly as it was. Whizi does this on the website. Under every finished reply there is a Branch button: it copies the chat up to and including that reply into a new chat, opens it, and confirms "Branched into a new chat." The original conversation is not touched. To copy the whole conversation instead, open the chat options menu in the sidebar and choose Duplicate chat.
Message versions are a different thing. Editing a message you already sent replaces the tail of the same conversation and files the tail it replaced as a version you can flip back to. That is a branch you can visit, not one you can run in parallel: exactly one version is live at any moment. Branch is the parallel option, because it gives the other path a chat of its own.
"Fork" means four different things in practice, so start from which one you wanted:
| What you wanted | What to use | What actually happens |
|---|---|---|
| A different path from a midpoint, with the original kept | Branch under that reply | A new chat with everything up to and including that reply, and the original stays as it was |
| A full copy of the conversation | Duplicate chat in the chat options menu | A new chat with the whole active history |
| A different answer inside the same chat | Edit that message and send it again | The tail is replaced, and the old tail is archived as a version |
| A side question that does not pollute the thread | A new chat | Nothing carries over except what you paste in |
| The same standing context across several chats | A project | Instructions and pinned files apply to every chat in it |
| A copy someone else can continue | Not available | A share link is a read-only view |
How to branch a chat in Whizi
Sign in on the website and open a saved chat. Every finished reply has a Branch button in the row under it. One click copies the chat up to and including that reply into a new chat, opens it straight away and confirms "Branched into a new chat." To copy the whole conversation, open that chat's options menu in the sidebar and choose Duplicate chat.
The copy takes the active history, the chat's files along with the attachments on the copied messages, the chosen model, the web search setting, and the project the chat belongs to. A PDF you discussed in the original is still there in the branch. Very long chats are cut to their most recent 400 messages, because a continuation builds on the newest ones.
What stays behind is the archived versions of edited messages and any share links. The new chat, like every Whizi chat, holds exactly one active branch, and branching does not change the original. Branch and Duplicate chat are on the website; the iPhone and Android apps do not have either yet.
The difference from editing matters most. Editing a message replaces the tail in the same chat and discards the stored versions of every turn beneath it. If you want to keep both paths, branch first and then edit inside the branch. The mechanics of editing, and what a version switch costs and can fail with, are on regenerate and edit messages.
What a new chat carries over
Starting a new chat is the honest answer to a side question, but it is worth being precise about what a new chat starts with, because "start a new chat" is only a real answer if you know what you are giving up.
A new chat starts empty. The previous conversation is not summarized into it, attachments are not re-attached, and the model has no view of the other thread. Whatever you want carried across, you carry across: every message and every code block has a copy control, so lifting the two or three answers that matter into the new chat takes a few seconds.
Two things do carry without pasting. Project instructions and pinned files apply to every conversation inside that project, so a new chat created in a project starts with that standing context already folded into the prompt. And a chat can be moved into a project or back out of it after the fact, which is the closest thing Whizi has to reparenting a conversation. The caps and the behavior are on how to use Projects.
The other route people reach for is model switching, and it is worth saying what it is not. Switching models inside a conversation carries the whole thread to the new model rather than copying it into a second chat. There is one thread throughout, and the replies above the switch stay credited to whichever model wrote them. The patterns are on switching models mid-conversation.
Two cases where something other than a fork works better
Comparing two answers to the same prompt. This is the most common reason to want a fork, and a fork is the long way round: send the prompt to two models in two columns and read the outputs next to each other. Neither model sees the other output, which is the entire value of the comparison. That is on comparing models side by side, a Pro and Powerhouse feature.
Keeping part of a thread away from a model. A branch carries everything up to the reply you pick, including the context that is getting in the way. When the long history itself is the problem, the move is a new chat seeded with a short summary of what actually matters. A clean start has its own case anyway: a long thread makes older context compete for attention with the real question, so three sentences of setup often read better than forty messages of history.
If what you want is a copy for someone else rather than for yourself, sharing produces a public link to one conversation and the recipient reads a sanitized, read-only view of it. They cannot continue it, and it is not a fork in their account either. The details, including revoking a link, are on sharing a conversation.
For a copy of everything you have, Settings has an Export data action that produces your chats and messages, projects and their file metadata, media, share links, subscription and referral profile. It is an archive rather than a re-importable branch: Whizi imports ChatGPT and Claude exports, not its own.
- On the website, Branch under a reply copies the chat up to there into a new chat
- Duplicate chat in the chat options menu copies the whole conversation
- Files, model, web search setting and project come along; archived versions and share links do not
- Edit and resend replaces the tail in the same chat and archives the old one as a version
- Only one version is live at a time, so versions are visited rather than run in parallel
- Editing a turn discards the stored versions of every turn beneath it, so branch first if you want to keep a later path
- A new chat starts empty; only project instructions and pinned files carry over without pasting
- A share link is a read-only view and cannot be continued by the recipient
Frequently asked questions
How do I fork a chat in Whizi?
On the website, signed in and in a saved chat, click Branch under the reply you want to fork from. Whizi copies the chat up to and including that reply into a new chat and opens it, and the original stays as it was. To copy the whole conversation, choose Duplicate chat in the chat options menu in the sidebar. The iPhone and Android apps do not have either yet.
Can I duplicate a chat so the original stays untouched?
Yes. On the website, open the chat options menu in the sidebar and choose Duplicate chat. The copy opens as a new chat with the active history, the files, the model and the project, and nothing you do in it changes the original. Branch under a reply does the same thing but stops at that reply.
What does fork chat mean, and how is it different from a version?
A version is one of several stored tails for the same turn, and exactly one of them is live at a time. You move between them with the arrows on the edited turn, and switching swaps the whole tail rather than one bubble. A fork, which Whizi calls a branch, is a separate new chat where you keep writing in parallel while the original stays as it was. Versions are covered on regenerate and edit messages.
If I start a new chat, does the model remember the old one?
Not from the old conversation itself. A new chat starts empty and the model receives only what is in that chat. The exception is a project: instructions and pinned files apply to every conversation inside it, so a chat created in a project already carries that context. Anything else has to be pasted in, and every message carries a copy control for exactly that.
Can I branch a conversation to try a different model?
You do not need a branch for that. Switching the model inside a conversation carries the existing thread to the new model, and each reply stays credited to whichever model produced it, so one thread holds the whole comparison. If you want two answers to the same prompt rather than a handover, send it to two models side by side instead, which is a Pro and Powerhouse feature.
Will editing an early message lose my later branches?
Yes, and this is the one surprise worth knowing in advance. Editing a turn discards the stored versions of every turn after it, because those versions hang off a conversation that no longer exists. If you want to keep a later path, branch the chat before you edit, and if you are reworking several turns in the same chat, edit the earliest one last.