Managed settings failures now name the reason and warn that proxy settings aren't applied.
What's wrong with this entry?
When Claude Code cannot fetch your organization's managed settings, the message now names the reason (401/403, other 4xx/5xx, timeout, network, parse error, invalid settings, or a gateway-pin mismatch). If it falls back to a cached copy, it also tells you that transport environment settings from that policy are not applied.
- On a stale cache, proxy, CA certificate and provider environment values from managed policy are withheld until a fetch succeeds; the rest of the cached settings still apply.
; proxy/CA/provider env withheld until a fetch succeeds
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.224
Org-anchored consent for remote managed settings
Both mention managed
-
v2.1.224
Consent to dangerous remote settings is remembered per organization
Both mention managed
-
v2.1.228
Managed policy helper failures throw instead of returning text
Both mention managed