Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.261 ·

Overage-included-models usage display is data-driven from an empty-by-default allowlist

A display for overage-included models exists but has an empty allowlist until set remotely.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.261
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
In DevelopmentKind: in v2.1.261,
What probably matters to youSection of the release

A new usage-limit display can show which models are included under overage ("weekly_scoped"), refreshing its list from GrowthBook once the data source moves off fallback/disk. The underlying allowlist, gate tengu_usage_overage_included_models, defaults to an empty array, so this new display currently has nothing to show until a remote value is set.

Read from
Feature flag
tengu_usage_overage_included_models Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.261: no gate table built for this version

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.261. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns ["Fable","Fable 5","Fable 5.1","Fable 5.2","Mythos 5.2"] for tengu_usage_overage_included_models, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.261 →

Feedback