Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.293 ·

Model choices now depend on your billing state

Automatic moves to a larger-context model and Fable-style model handling now check how the account is billed and whether extra usage was agreed

Group of 2 You'll notice Internal Changes
JSON All of v2.1.293
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ModelsArea: what it touches
Internal ChangesKind: in v2.1.293,
What probably matters to youSection of the release

Unclear It is not clear what this model-specific behaviour does for a user who gets it.

What

A new helper sorts each account into a billing state: pay_per_request, admin_billed, included_in_plan, needs_consent, needs_credits, out_of_credits or consented. Two model checks now use it.

  • The automatic switch to a model with a larger context window, used when the conversation is about to be too long, now also calls Mar. Mar allows the switch when the model is not recognised, the account is pay-per-request or admin-billed, or you have agreed to extra usage and have credits. The old Bve(w) condition was removed.
  • The path for Fable and similar models now applies when the model family's billing mode is neither pay_per_request nor included_in_plan.

Why

Accounts that have not agreed to extra usage, or have no credits, will likely no longer be moved to the bigger-context model automatically. That avoids charges you did not agree to. Which accounts see the Fable-specific behaviour now depends on how the account is billed.

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 what this model-specific behaviour does for a user who gets it.

See this entry in the whole of v2.1.293 →

Feedback