Claude Code can ask the API which models exist and store their capabilities, but the fetch is short-circuited.
A model-capability fetch is written and saved to disk, but a guard stops the network call entirely in this build.
What's wrong with this entry?
A new routine asks the API for the list of models, records a capability entry for each and saves them. Two guard checks run before any network call and one of them short-circuits it entirely in this build, so no fetch happens. Failures log a single line.
- The request can optionally carry a beta header.
- The failure line is prefixed
[modelCapabilities] fetch failed:.
[modelCapabilities] fetch failed:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Search field in the model picker
Both mention model
-
v2.1.236
Cancellable waits when
/modeltalks to a cloud sessionBoth mention model
-
v2.1.238
Model and effort switch warning now checks whether the cache is actually warm
Both mention model