Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Model catalog resolution now takes an explicit provenance argument

Model catalog resolution now passes a provenance value when rebuilding the catalog

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaElsewherewhat it touches
KindInternal Changesin v2.1.265,
Under the hood

Model catalog resolution now passes a provenance value when rebuilding the catalog

What

The internal function that reconciles the model picker's catalog state now calls the catalog builder with an object that includes a provenance field (tracking where the catalog data came from), instead of just passing the raw catalog value as before.

Why

This is an internal refactor to the model catalog machinery. The evidence doesn't show what using provenance changes for a user of the model picker.

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 doubtWhat the provenance value is used for, or what changes for the user, is not shown by the evidence.

See this entry in the whole of v2.1.265 →

Feedback