Simple Chat

Fork a conversation

Branch an existing chat so you can explore a different direction without changing the original thread.

What this does

Forking creates a new conversation from an existing point in a chat. The original thread remains available while the fork continues independently.

Video planned

Fork a conversation walkthrough

Recording planned. Show fork a conversation end to end and explain why this task helps a user.

To publish this video:

  1. Upload the recording to YouTube or Microsoft Stream.
  2. Save a poster frame as docs/images/video-posters/guide-fork-a-conversation.png.
  3. Add the watch URL to this slot in docs/_data/media.yml.

Why you would use this

Fork a conversation when one path should continue as-is and another needs a different assumption, audience, model, or source set. It replaces copying previous context into a new chat by hand; it is unnecessary for a simple follow-up that belongs in the same thread.

Before you start

  • Collaborative conversation behavior depends on enable_collaborative_conversations.
  • You must be able to open the conversation you want to fork.
  • If workspace grounding was used, you still need access to the related documents.

Steps

  1. Open Chat and select the conversation to branch.
  2. Open the message actions menu at the point you want to branch from.
  3. Select Fork conversation.

Screenshot needed

Fork a conversation step 3

Capture the fork a conversation task at this step in SimpleChat with realistic sample data and redact secrets.

Save as docs/images/guides/fork-a-conversation-step-3.png

Drop the file at that path and it replaces this card automatically. No other change needed.

  1. In the confirmation modal, select Fork conversation again.
  2. Continue in the new conversation with the alternate direction.

Screenshot needed

Fork a conversation step 5

Capture the fork a conversation task at this step in SimpleChat with realistic sample data and redact secrets.

Save as docs/images/guides/fork-a-conversation-step-5.png

Drop the file at that path and it replaces this card automatically. No other change needed.

  1. Rename the forked conversation if the title does not clearly describe the new path.

Verify it worked

A new conversation opens or appears in the list. The original conversation remains unchanged.

Troubleshooting

Symptom Likely cause Fix
Fork conversation is not available That message or conversation type does not expose the action Start a new chat manually or export the transcript if you need a copy.
The fork cannot use prior documents Your document access changed Re-select accessible documents with Workspaces.