Skip to main content

Branch From Range Feature

Feature Request

My understanding is that the T3 branching feature will branch always branch from the very first message in the chat conversation to the message that the user wants to branch to. However, many times I don’t want to branch from the very first message. Sometimes, I want to branch from a specific point midway in the conversation to another point further on in the conversation (Branch to).

Status: Gathering Interest1 comment

Log in to comment and vote

Comments1

  • Brown Mole

    +1 for this. The current behavior of always copying everything from message 1 to the branch point is the biggest reason branched threads hit context limits and slow down so quickly.

    Along with a range-based branch, another natural extension to branching would be a metadata or summary-based branch:

    Instead of duplicating the full raw message history, the branch could compile the conversation up to that point (or a selected range) into a structured context snapshot.

    A few thoughts on how that could work:

    • Distilled context primer: A quick background pass generates a concise summary of key constraints, decisions, and current state, then seeds the new branch with just that metadata.

    • Editable snapshot: A brief modal lets you preview and tweak the summary before launching the new chat, so you can discard dead ends or outdated assumptions.

    • Context hygiene: You get full continuity from the parent thread without the token bloat, latency, and context drift that come from dragging along dozens of back-and-forth turns.

    Both range branching and summary branching tackle the exact same pain point—giving users granular control over what context actually carries over into a new branch.