Repository navigation
Branch a thread into parallel attempts on different providers, compare the diffs, merge the winner #34546
AryanKansagara
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
I often don't know which provider or model will handle a task best until I see the result. For anything with taste or judgment, like UI work, a refactor or an API design, I want to try the same step with two providers and keep the better result.
T3 Code already has most of the pieces: I can fork a thread from a message, a fork to another provider carries the conversation over through a portable handoff, and worktrees isolate changes. But comparing attempts still means:
Each step exists, but together they're slow enough that I usually skip comparing and settle for whichever provider I started with.
Proposal
Branch to… at the current point of a thread. In effect, a fork into several providers at once, plus a way to compare and keep one.
Ways back:
Visibility: each pane header shows the branch's provider, model, status and token use. The sidebar groups branches under the parent thread.
Non-goals
What's new compared to duplicating a thread
#20267 proposes duplicating a thread to try a different direction, and explicitly leaves out merge-back. This proposal shares that starting point (fork the thread), but the new parts are running several providers in parallel, comparing their diffs, and merging the chosen result back. Without merge-back, comparing attempts still ends in copying changes by hand. If the smaller "Duplicate thread" menu item suggested in #20267 is approved, "Branch to…" could sit next to it in the same menu.
Open questions for maintainers
Related
@providerin the composer to start a subagent or new threadAll reactions