Multi-model comparison and message branching

Multi-model comparison is suitable for problems without a single correct answer, such as solution reviews, copy direction, and cross-checking materials. Message branching lets you try another route from a certain node without duplicating the entire conversation.

Compare multiple models at the same time

1

1. Open [Chat] and click the model name

Select the models you want to compare in the model picker. Before using it for the first time, first make sure the services these models belong to can connect normally.

2

2. Send the same question

Include the evaluation criteria in the question, for example, “Compare from the perspectives of feasibility, risk, and cost.” Don’t just ask, “Which is better?”

3

3. Compare the differences, rather than just choosing the longest answer

Focus on whether the facts are consistent, whether the assumptions are clear, what has been omitted, and which option better fits your constraints. Important facts should still be checked against the original source material.

Select multiple models from the model picker, then use the same question to compare the differences.

Selecting multiple models at once will send separate requests. When fees, speed, or sensitive data are involved, first use a short question to confirm the connection and results, then handle longer materials.

Create a branch from a message

Find the message you want to explore again, open the message menu, and choose the branch option. The new branch will retain the previous context, and subsequent messages will be recorded separately from the original path. Use the branch manager to switch between paths, compare them, and go back.

You can also create an empty branch in the branch canvas. After creation, an empty branch is saved immediately, remains after restarting the app, and stays on the branch canvas; the next time you send something in the input box, that branch will be filled in. Empty branches you no longer need can be deleted from the node’s right-click menu.

The branch manager keeps both the pre-launch checklist and the quick pilot routes.

In the figure: ① branch nodes and the current path; ② legends for users, assistants, current path, and deactivated paths. The example retains the two routes “Pre-launch Checklist” and “Quick Pilot,” with a total of 2 branches and 6 message nodes.

Use case: reviewing two release plans

First ask the model to identify the risks and gaps in the plans, then follow up from the same reply with “add the pre-launch checklist” and “evaluate from the quick pilot perspective.” After opening the branch manager, the two routes will be kept side by side, and you can continue asking questions on each separately or return to the other route at any time to verify conclusions.

When is it not suitable to open multiple models?

If you are only looking up one clear fact, organizing a short text, or the material contains content that should not be sent to multiple service providers, using a single model is more appropriate.

Will branching modify the original message?

No. A branch continues from the selected node, and the original path remains intact and can be returned to at any time.