Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Usage records gain a fallback_credit field

API usage records now carry an optional fallback_credit field, which reports the outcome of a fallback-credit token a request presented

Group of 2 Under the hood Internal Changes
JSON All of v2.1.285
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
UsageArea: what it touches
Internal ChangesKind: in v2.1.285,
Internal ChangesSection of the release

What

The usage information attached to each API response, which records things like how many tokens a request used, now has a fallback_credit field.

  • fallback_credit is optional in the usage schema. It is described as the outcome of a fallback-credit token the request presented, or null.
  • It defaults to null and is carried through when usage from several requests is combined.

Why

This is a data change that most people will not see directly. If you read the usage data Claude Code records or reports, expect a new fallback_credit field. It will be null unless a request presented a fallback-credit token.

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 how the fallback_credit value is used.

See this entry in the whole of v2.1.285 →

Feedback