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.260 ·

Fable model visibility now gated by a server-verified entitlement probe

Fable eligibility now has a second unlock path via a cached entitlement probe result.

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

The function deciding fable-model eligibility changed hL(oK) to hL(SO) || Iwt() in two branches. Iwt() returns true only when awt() === "accepted", and awt() reads a fableEntitlementProbe (fableEntitlementProbeAccount, fableEntitlementProbeModel) cached on the provider state (Rr().providerCache), populated by an async probe/acceptance flow keyed to the current account.

The model-picker logic (koe) now conditionally injects an extra model option ($G(o, pQr(pq(), e))) into the list before the usual custom/alias model handling, gated through the same Iwt() check; absent an accepted probe result the function returns undefined/false. This means a session can become fable-eligible purely via the probe's cached 'accepted' result even when the existing hL provider-list check fails. Related identifiers claude-fable- and the alias fable51 show this is a codenamed model whose visibility depends on a server-verified entitlement rather than a local flag; it isn't fully traced what sets the probe to 'accepted', so how often this path fires isn't known.

Read from
Names in the bundlefableEntitlementProbe

See this entry in the whole of v2.1.260 →

Feedback