Metadata / Summary-Based Branching

Problem

Branching currently copies raw message history verbatim. In long threads, this:

Eats context: Consumes valuable context window space before new work begins.
Adds noise: Carries forward superseded code, dead ends, and tangents.
Increases latency: Slows down inference with bloated prompt payloads.

Proposed Solution

Add an option to branch via a compiled context summary rather than copying the raw transcript. The new branch starts lean, seeded with a structured briefing of the discussion up to that point.

Workflow

Branch selection: When branching, choose between Full Clone or Summary Branch.
Auto-synthesis: Generates a brief snapshot of goals, decisions made, active constraints, and current code state.
Editable preview: An optional modal lets the user tweak or prune the summary before creating the branch.
Clean initiation The summary is injected as the new thread's initial primer, retaining a backlink to the parent thread for traceability.

Benefits

Maximizes available context headroom for the new branch.
Keeps model attention sharp by shedding irrelevant conversational history.
Pairs naturally with range-based branching to preserve early context without the raw bloat.