Stale model/effort label

“The session really runs on the new model, but the bottom-bar label and the app's session record keep the old model and effort.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/19185/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Growing. 1 report in the last 7 days and none the week before, down from 2 a week at the late-October peak.

Desktop model and effort label stays stale after in-session change. In the Code tab, the label under the prompt and the app's session record keep the old model after /model, /effort or $.command.run.

Is this your bug?

File my report

Where: Desktop Code tab
Versions: 2.1.293 to 2.1.309
Platforms: macOS
How bad: Breaks a normal workflow.

Part of: Session model choice not respected3 bugs

Session model pick becomes default6 people
Gateway aliases pick older models2 people

Not quite your bug?

New sessions ignore default model2 people
No 1M Opus in Desktop2 people

Original reports3, newest first

Nov 1, 2026Desktop app: model/effort label doesn't update when the session changes model via /model or /effort#106639
Oct 19, 2026Desktop app: model picker/readout stays stale after a mod runs $.command.run({ command: "model" })#103584
Oct 18, 2026Desktop: model/effort label stays stale when the model is switched outside the composer (plugin $.command.run('/model'))#103205