Ask a hard question in five chat windows and you’ll end up with five essays. Four of them will say “it depends,” in slightly different fonts. It feels like research. It’s filing.
The structural problem is simple: independent answers never meet. Nothing in the workflow forces the Gemini answer to confront the Claude answer. You become the courier between them, pasting summaries into each other, and the “discussion” runs at the speed of copy-paste. Worse, long parallel answers reward skimming: most people anchor on the first answer they finish reading and call the rest of it diligence.
The format change: put the models in the same room
You don’t need a new model. You need a room where each participant hears the whole conversation before their turn, and where you can actually interrupt.
Live multi-party voice calls with AI participants make that possible: a small cast (two to eight) generated around the decision you type in, each with a role and a disposition, talking out loud, reacting to each other instead of to a fresh prompt. If you want to see the idea in text form, Andrej Karpathy’s “LLM Council” write-up describes a judge-and-council pattern; voice just removes the courier. (We build one such app, AI Group Call, disclosure up front. The chairing advice below works with any multi-participant setup, including a group chat and a human referee: you.)
How to chair a room of AIs
Frame a decision, not a topic. “Should we add a caching layer before launch: yes or no, one reason each” produces arguments. “Thoughts on caching?” produces textbooks. The room is only as sharp as the question’s edges.
Collect opening positions before discussion. Ask every seat to commit in one line. Panels without stated positions drift into polite agreement within three turns; the first speaker anchors everyone.
Name the disagreements. “What is wrong with the second answer?” gets much harder critique than “any objections?” People are politer than asked; so are models, unless the question forces the conflict.
Keep a skeptic in the room. If your setup doesn’t seed one by default (ours does for rooms of four or more), assign one explicitly: “For your next two turns, your job is to argue the strongest case against where this conversation is heading.” Watch whether the recommendation survives it. Most weak consensus dies right there, which is the point.
Bring receipts. Paste the error message, the churn numbers, the screenshot. A room argues far better with real constraints in front of it than with your summary of them.
Close with a vote and keep the transcript. One line each: what would change your mind, then what you’d do. The transcript is the actual deliverable. A month later you can check which voice was right, and calibrate who to trust for which kind of call.
What the format is not
It is not a benchmark, not a legal board, not a way to get five independent essays faster. Spoken turns are short by nature: good for trade-offs, follow-ups, and “why,” bad for long proofs and code review. If the task is “read this spec and find the bug,” go back to the chat window. If the task is “I have two options and a deadline,” a room that argues out loud gets you to a decision in twenty minutes instead of an inbox of essays you’ll never re-read.
The instruments exist now. Most people are still using filing cabinets.