Product·Auto Model Mode

Pick Auto.
Continuum picks the team.

Auto Model Mode is a BYOK router across planner, executor, and verifier roles—on the hosts you already run. Score-based selection, role stamps that show which model ran each step, ask-first plan approval, and Cancel as the brake. Honest v1: it is not quota-aware yet.

Download for Mac Read the docs
CodeUsageSettings
auto
São Paulo · AutoBYOK · your providers
planner fable-5 score 0.91
executor gpt-5.5 score 0.87
verifier grok score 0.84
role routingnot quota-aware · v1
01 · Roles

Planner. Executor. Verifier.

Auto doesn’t mean “mystery model.” It means Continuum assigns roles across the providers you connected: one model plans, one implements, one checks. Each hop can land on a different host in your fleet.

You still own every login. Continuum only routes work among keys and machines you already pay for.

three roles cross-host BYOK only
01 plan

scope · steps · risks

→
02 execute

edits · tests · tools

→
03 verify

review · gate · ship

Code
scores
fable-5
0.91
gpt-5.5
0.87
composer
0.72
grok
0.84
scores · task fit · not hidden magic
02 · Score-based routing

Picks you can inspect.

Selection is score-based—task fit across the models available in your catalog—not a black-box vendor ranking. When Auto assigns a role, you can see why that model was in the running.

Availability still matters: a provider that isn’t connected or is disabled never enters the pool.

03 · Role stamps

See which model ran.

Transcript steps carry role stamps—planner / executor / verifier plus the model id—so a multi-model run never becomes an unattributable blur. Cost and tokens still roll up honestly under each provider.

If something goes wrong, you know which role to re-run, not “the AI.”

Code
stamps
planner · fable-5

4-step migration plan ready for approval.

executor · gpt-5.5

Applied parser isolation; tests running.

verifier · grok

Diff review: +212 −96 · no secrets in patch.

Auto planask first
Planner proposes steps
You approve before execute
cancel the brake · stops the run
04 · Ask-first & cancel

Auto never means unsupervised.

Ask-first plan approval keeps a human gate before the executor writes. Same plan card, same Approve path as manual plan mode in the Code workbench.

Cancel is the brake—interrupt the active role immediately. Auto is a router with a kill switch, not a runaway swarm. Details on plan & review.

05 · Honest limits

Not quota-aware in v1.

Auto does not yet read live rate-limit gauges when picking models. It won’t automatically dodge a 95% Claude window. Watch the menu-bar gauges yourself, pin accounts, or pick models manually when a window is hot.

We’d rather say that up front than pretend the router is smarter about caps than it is. Quota-aware routing is a later chapter. See gauges and multi-account.

v1 does
  • role routing across BYOK models
  • score-based selection you can see
  • stamps · ask-first · cancel
v1 does not
  • quota / rate-limit avoidance
  • silent spend caps
  • unattended multi-hour fleets
06 · Questions

The honest fine print.

Short answers here, long answers in the docs.

No. Auto routes among providers you already connected (BYOK). Continuum is not selling a mystery model under the Auto name.

Cancel stops the active work. You can continue the session with a manual model pick for the next turn—Auto doesn’t lock you out of the composer.

Yes when the host can spawn the selected providers. Role work still runs on your hardware; controllers only steer.

Not in v1. That limitation is intentional product honesty. Use gauges, multi-account pins, or manual selection when a window is hot.

07 · Begin

Let Auto draft the team.
You still approve the plan.

Connect two providers, start a Code session, pick Auto.

Download for Mac Read the docs

see also · code · providers · plan & review