Ways people use GPTree
Get three models' feedback on a spec, merged into one review
Paste a plan or spec from your coding agent, have three models review it side by side, and send back one merged piece of feedback instead of three tabs of opinions.
Coding agents like Claude Code and Cursor write plans before they write code, and the plan is the cheapest place to catch a mistake. The problem with one reviewer is the same for models as for people: a single opinion has blind spots, and you can't see them from inside it. The fix is boringly effective, ask three reviewers, but doing that across three browser tabs means you become the merge tool, rereading everything, deciding what overlaps, and typing the synthesis yourself.
GPTree runs that whole loop as one motion. Paste the spec into a conversation with a request like "Review this plan; give feedback and suggested improvements," and press Explore instead of Send. The Compare models preset already holds three models from different providers; launch it and the three reviews stream in side by side.
When they settle, GPTree scores the answers against your prompt and marks a winner with a written rationale, so you know where to start reading. The compare drawer summarizes what each review uniquely contributes, which is how you spot the reviewer who noticed the missing rollback plan while the other two argued about naming.
Then merge. "Merge all into one answer" collects every successful review, and the merge dialog asks what the final answer should be. This is the step that decides whether you get a document you can use: say "merged feedback on this spec, addressed to its author" and the output is written as exactly that, concrete points preserved, contradictions resolved, no essay about comparison methodology. It runs on the strongest model from your comparison by default, and the preview has a Copy Markdown button, because the destination of this document is your coding agent's chat window, not a filing cabinet.
Paste the merged review back to Claude Code and let it revise the plan. The whole tree, spec, three reviews, merged verdict, stays in GPTree, so when the agent's next revision lands you can run the same comparison again in the same place and see what actually improved.
The habit worth building: any time an agent hands you a plan you're about to approve, that approval is worth three model-minutes. One Explore, one Merge, one paste back.