Account and Models
Tune how your panel deliberates — review style, per-seat model overrides, and what "Use system default" really means.
Two settings change how your runs deliberate, independent of what your admin configured for everyone: the review style and your model overrides. Both live in Settings → Account → General.
Review style
Controls the posture of the reviewing model — the seat that critiques the first draft.
Balanced critique
A neutral reviewer: it improves the draft, flags weaknesses, and fills gaps, without manufacturing disagreement. Best for editing passes and questions where you want the answer strengthened.
Opposing view
An adversarial reviewer: it builds the strongest credible case against the draft, even when it largely agrees. Best when you're pressure-testing a decision — if the answer survives a motivated opponent, it's probably sound.
Rule of thumb
Model overrides
Every mode has named seats, and every seat has a system default chosen by your admin. Overrides let you pin a specific model to any seat, for your account only:
| Mode | Seats you can override |
|---|---|
| Relay | Model A · Model B · Synthesizer |
| Debate | Model A · Model B · Synthesizer |
| Moot | Generator · Sceptic · Specialist · Chair |
Practical reasons to override:
- You've found a model that's stronger at your domain — pin it to the Generator.
- You want maximum friction — pin models from different providers to opposing seats, so shared training habits don't produce polite agreement.
- You're comparing models — pin a candidate to one seat and watch how it argues.
You can also override the model pair for a single run from the composer toolbar, without touching your saved settings.
"Use system default" — the setting that keeps you current
Every seat offers Use system default, and it's the right choice for most seats, most of the time:
- You inherit the admin-managed role matrix.
- When your admin upgrades a default (say, to a newer model generation), you get the upgrade automatically.
- You only pin the seats you actually have opinions about; everything else keeps tracking the shared config.
A pinned seat, by contrast, stays pinned until you change it — including after the roster around it improves.
The boundaries
Personal overrides work within the shared roster, not around it:
- You can only choose from models your admin has enabled in the roster.
- If an admin later disables a model you pinned, your runs fall back to the system default for that seat.
- Whether a seat can see images depends on the pinned model's vision capability — the composer warns with "Can't see images" when your current selection can't.