Several opinions at once
Tick more than one subscription and the same task runs on each, every agent with its own model — and what the router remembers, per project, from the times you disagree with it.
The router’s proposal is one line in a checklist of every subscription able to take that level — the ones marked eligible for it in Settings → Routing. Claude and Codex come pre-mapped; tick the others for the levels you want them to take, with or without a model.
That single control covers three situations:
- leave the router’s box ticked — you accept;
- untick it and tick another — you contradict it;
- tick several — you want several answers.
Several answers
Each ticked subscription starts the same brief in its own session, and each one gets its own model for the level. Imposing the first agent’s settings on the others would be asking the same question twice.
The marginal cost is zero: those plans are already paid for. A router billed per token cannot offer this, because for its operator every redundant run is real money — which is exactly why such routers are built to remove redundancy.
What it does consume is a launch on each subscription’s quota window. The gauges show it.
What the router remembers, per project
It watches your recent launches on that project, and reads only the deliberate gestures:
| Gesture | Effect |
|---|---|
| You accept the proposal | Nothing is remembered — you may simply have had no opinion |
| You force another CLI | That CLI is favoured next time; the one it replaced less so |
| You ask a second subscription | That CLI is favoured, more mildly |
It stays a preference between CLIs that were already eligible, never a rule, and it never makes a CLI eligible that was not.
The window is counted in launches rather than in days, on purpose: habits change with the phase of a project — exploration, then production, then maintenance — and a calendar window keeps gestures that no longer describe the current work.
The panel says what it picked up from this project and which CLIs it now favours, next to a Forget button. A preference you cannot erase is an opinion imposed on you.
Where it is stored
In your OFM config directory, per project, alongside the quota gauges and the eligible-fallback list. Nothing about your projects leaves the machine to feed routing. See Data & file locations.
Frequently asked
- Does asking two agents cost twice as much?
- Not in money. Both plans are already paid, so the marginal cost is zero; what it consumes is quota on both subscriptions, which the gauges show.
- Can I erase what the router remembers?
- Yes. The panel shows what it picked up from this project and a Forget button clears it.