Branching / Forking Conversations

CharlieJ
Mon, 18 Aug 2025 11:39:59 +0000
Feature Requests

Feature Request

The ability to branch / fork a conversation so all follow ups / questions aren’t contained in a single thread.

Problem Statement

When I chat to an LLM sometimes I have multiple questions about a response, especially if it’s longer. But these can be discrete ideas / thought processes. I start by asking my first question, maybe then need to follow up once or twice. Then I ask the next question and the same thing happens again, this can lead to threads becoming very long and incoherent.

Proposed Solution

There should be a button on the UI when asking a follow up question that allows the user to fork that conversation into either a separate thread entirely, or just a smaller sub-conversation which can then be collapsible / looked back on within the same thread.

Users should be able to fork a conversation multiple times.

API Impact

Which API component is affected?

This wouldn’t be specifically API based and personally I don’t use the API so I’m not deeply sure of what would be affected. My initial thoughts are retrieval of threads / full conversations, maybe you could just retrieve a specific fork instead of a full thread

Is this related to a specific model? Unrelated to a specific model

Would this require new API parameters or changes to existing ones? May require new parameters / filters, but also doesn’t entirely need it

Alternatives Considered

The only real work arounds are to start a new thread or keep all the information in the same thread. This is more of a UX based improvement more than anything else as the current options either lead to very long, sometimes incoherent threads, or mean you have to switch between threads sometimes losing track of context / where specific information lies.

5 posts - 4 participants