Council
Send one chat turn to a council of models. Several engines answer at once, review each other anonymously, and your chat's own model synthesizes a single reply. It is advisory and read-only.
Some turns deserve more than one opinion. Council sends a single chat turn to several models at once, then hands you one answer.
Ask a turn to several models
Type /council and it arms your next message. Write the request as you normally would, and instead of one engine replying, several do, at the same time.
It runs in place. No new tab opens and the thread keeps its own model. The council does its work behind that one turn, and the synthesized answer streams into the same conversation as the reply.
They cross-check each other
The members are anonymized, shown as Member A, Member B and so on rather than by engine or model. When cross-review is on, each member reads the others' answers with the names hidden, ranks them by accuracy and insight, and cannot reveal or guess who wrote which.
That anonymity is the point: an answer wins on its merits, not on which model it came from, and a single model's blind spot is less likely to survive contact with the others.
Your chat model has the final word
The chairman is your thread's own model. It already holds the full conversation and the voice the thread has been speaking in, so it is the one that reconciles the disagreements, keeps what is strongest, and writes a single reply in that voice. It does not paste the members' answers back to you or name them; it synthesizes.
The same context, several readings
Each member starts from the same path-scoped memories, rules and skills for the path you are working in, plus a brief of the conversation so far. So a council is several engines reading the same product knowledge and the same constraints, not several sessions you would have to explain your product to one by one.
Advisory by design
Members are told, in plain terms, not to modify any repository files. Council is for a decision rather than a change: an architecture call, a tricky trade-off, a design someone wants sanity-checked, a review before you commit to a direction. When you want the work actually done, that is what Workflow is for.
From the engines you already have
The members are the local engines you already installed and signed into, running under your own subscriptions rather than a hosted catalogue billed by the token.
Readiness is checked first. An engine that is not both installed and authenticated cannot take a seat, so it is substituted with the next ready engine or, if none remain, the seat is dropped and surfaced to you rather than silently missing. Below two usable members there is no council to run, so the turn falls back to a single normal answer with a note that it did.