Skip to main content
Compare engines

Compare engines

Vresk keeps several engines on one shelf, which raises an honest question: which one is right for your work? Compare answers it directly. Ask once, watch two or three engines answer side by side, and keep the one that earned it.

Arming a comparison

Next to the engine picker at the top of a chat there is a Compare button. It opens the same shelf you already pick engines from — this time you are picking a set.

  1. Pick two or three engines

    Two is the minimum, three is the cap — the whole point here is choosing for yourself.
  2. Send your message as usual

    Every engine you picked answers it, side by side, each in its own pane.

Arming is sticky: the button shows how many engines are armed, and each message you send is compared until you press Clear in the picker or keep a winner. Which engines are worth auditioning is its own question — choosing an engine covers the shelf.

Compare needs a free account

Comparing runs several engines on your behalf, so it is for signed-in users only. As a guest you can still open the picker — it tells you this and offers to create the account. Your conversation comes with you when you sign up; nothing is lost.

Reading the panes

Each pane is one engine’s complete answer — nothing is merged. The pane’s header names the engine and carries its origin mark, and the header stays put while you scroll the answer under it, so a pane you are deep into still says who wrote it.

Where there is room, the panes sit side by side, and a long-winded answer scrolls inside its own card rather than pushing the others off the screen. On a phone the panes stack full width instead. Engines finish at different speeds; a pane that has not started yet says it is waiting rather than sitting blank.

Engines can build things during a comparison, not just write. A working widget or page shows up as a card inside its engine’s pane — running, where that is safe to do — with an Expand control that opens it in the side panel.

Previews are for judging

Inside a pane, a built thing is a preview. Editing or repairing it happens after you expand it into the side panel — fixing a build is something you do to the one you picked, not to all three at once.

Keeping a winner

Every finished pane offers Keep this one at its foot. Tapping it is the decision the whole feature exists for, and it does four things at once:

  • The conversation is pinned to that engine — your next message is a normal single answer, served by the winner.
  • The winning pane is stamped Kept, and the message-level label now names it.
  • The other answers collapse to a Show this answer row — the comparison stays in your history, one click re-opens any of them.
  • Compare disarms. You are back to ordinary chat until you arm it again.

For a worked example of this flow end to end, see audition engines, keep one.

When an arm is cut short

Two or three engines answering at once means more chances for one of them to run long, stop early, or fail outright. Vresk does not paper over that — a comparison is exactly the wrong place to make an engine look better than it did.

A cut answer says so

An answer that hit its length limit or died mid-stream keeps what was already written and carries a notice saying what happened and what to do next. A build that was cut partway through shows a banner naming it incomplete rather than posing as finished. And an engine that returned nothing gets a plain sentence saying so — never an empty pane you have to interpret.