You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
Internal ChangesKind: in v2.1.299,
What probably matters to youSection of the release
Unclear What the override is keyed on and where it comes from is not known, so it is unclear when it changes the prompt.
What
When you use more than your plan includes, Claude Code may ask your consent to bill extra usage to usage credits. These checks can now be decided separately for each model:
Consent check: the function that decides whether overage or plan-limit consent is needed now takes an argument. It first looks for an override for that argument and, if one exists, uses that override's enabled value. Otherwise it falls back to the old checks (enabled === false, overageConsentRequired, planLimitsEndDate).
Per-model list: a GrowthBook flag (a remote setting), tengu_saffron_lattice, now carries a perModel map of {enabled} entries keyed by model id. Billing status such as needs_consent and needs_credits, and whether the Fable model is disabled in the model picker, are now worked out per model instead of plan-wide. If entries for one model conflict, that model is treated as billed to usage credits.
Nothing has been read about tengu_saffron_lattice yet, which means its state is unknown, not off.
Why
Which models need usage credits can now differ from model to model, so you may see a consent prompt or a disabled entry in the model picker for one model but not another.
