Failed managed-settings fetches now record a structured reason visible in debug logs.
What's wrong with this entry?
When Claude Code cannot fetch centrally managed settings, it now records a structured reason alongside whatever settings it has, so debug logs say what actually went wrong instead of just that a fetch failed.
- The failure carries an error kind, a message, and optionally the HTTP status and whether a gateway pin mismatched.
- The error kind is named in the debug output on both the stale-cache path and the no-cache path.
Remote settings: 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.236
Managed-settings review prompt dropped from the main UI
Both mention managed
-
v2.1.242
Startup can wait on a remote managed-settings refresh, with a deadline
Both mention managed
-
v2.1.246
Remote managed settings can defer their consent prompt to the next interactive session
Both mention managed