You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A run started with a model choice (--model, or the dashboard's model pick) that lands on the web path runs on whatever model claude.ai defaults to. Nothing says so: the choice is accepted and then dropped.
Mechanism (main 619e886e)
cli.ts:1254 puts model into the shared agent options, and the local driver honours it.
driver/cloud.ts:206 asks the daemon for a session with { repo, branch, prompt } only — no model.
dashboard/bridge-starts.ts queues exactly those three fields; the extension's content.jscreateSession picks the repo chip, the branch chip, fills the composer and sends. It never touches claude.ai's model picker.
Before #1694, claude --cloud passed --model through; the extension path (#1693) never had it, so the gap arrived with #1694.
Options
Drive the picker. Carry model through /_web-start → the start-queue → tf-create-session, and have content.js pick it in claude.ai's model menu before sending. Honours the choice; one more guessed selector on someone else's UI, so it is the fragile kind (every chip selector in createSession already reports rather than assumes).
Say it is ignored. Leave the session on the account's default and mark it on the run — a session event with no model already renders as "unknown" (Record the model on the run's meta #1438), so the honest minimum is a note on the run ("web runs use claude.ai's default model") and the dashboard not offering a model pick for a web run.
Option 2 is the cheap, honest baseline; option 1 can come on top if the default model turns out to matter for fan-out runs (the Opus-by-default rule for dogfood runs makes it likely).
What happens
A run started with a model choice (
--model, or the dashboard's model pick) that lands on the web path runs on whatever model claude.ai defaults to. Nothing says so: the choice is accepted and then dropped.Mechanism (main
619e886e)cli.ts:1254putsmodelinto the shared agent options, and the local driver honours it.driver/cloud.ts:206asks the daemon for a session with{ repo, branch, prompt }only — no model.dashboard/bridge-starts.tsqueues exactly those three fields; the extension'scontent.jscreateSessionpicks the repo chip, the branch chip, fills the composer and sends. It never touches claude.ai's model picker.Before #1694,
claude --cloudpassed--modelthrough; the extension path (#1693) never had it, so the gap arrived with #1694.Options
modelthrough/_web-start→ the start-queue →tf-create-session, and havecontent.jspick it in claude.ai's model menu before sending. Honours the choice; one more guessed selector on someone else's UI, so it is the fragile kind (every chip selector increateSessionalready reports rather than assumes).sessionevent with nomodelalready renders as "unknown" (Record the model on the run's meta #1438), so the honest minimum is a note on the run ("web runs use claude.ai's default model") and the dashboard not offering a model pick for a web run.Option 2 is the cheap, honest baseline; option 1 can come on top if the default model turns out to matter for fan-out runs (the Opus-by-default rule for dogfood runs makes it likely).
🤖 curated