Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Refused launch model is dropped in print and SDK sessions

In print/SDK sessions, a launch model the server refuses is now discarded if no turn has been sent yet, and the drop is recorded

Group of 2 You'll notice Bug Fixes
JSON All of v2.1.288
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SDKArea: what it touches
Bug FixesKind: in v2.1.288,
Bug FixesSection of the release

What

The launch model is the model a session starts with. In print and SDK sessions, which run Claude Code without the interactive screen, a set-model call can fail because the server refuses that model (serverRefusedModel). A new step, dropUnconfirmedLaunchModel, now discards the refused launch model if no turn has been sent yet. A turn is one exchange with the model.

  • dropUnconfirmedLaunchModel discards the refused launch model when no turn has been sent.
  • When that happens, Claude Code records a usage event that notes the surface the request came from and the error code.
  • refreshesClientDataOnSwitch is removed.
  • A clientDataFetches.clear() reset call is added.

Why

This affects which model a print or SDK session ends up using after the server turns down the model it was launched with. A refused launch model is no longer kept around once the server has said no, as long as no work has been sent yet.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which model the session uses instead once the refused one is dropped.

See this entry in the whole of v2.1.288 →

Feedback