Gateway settings failures now name the exact cause, from TLS mismatch to a rejected credential.
What's wrong with this entry?
When Claude Code cannot fetch managed settings from a Cloud gateway, it now shows a specific reason rather than a generic failure. Wording covers "couldn't connect to the gateway", "the gateway did not accept this session's credential", "no credential was on hand for the request", "the gateway's response was not valid managed settings", "the gateway's TLS certificate did not match the one you trusted", and "something unexpected went wrong (details with --debug)".
- The fetch returns a failure record carrying the error kind, the HTTP status, and whether the gateway's certificate pin mismatched, instead of a plain success/failure boolean.
- A certificate pin mismatch on the first request after login produces its own message beginning "Cloud gateway sign-in was not completed:" and the new credentials are discarded.
the gateway's response was not valid managed settings
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.247
Renaming a session warns when other sessions may keep the old name
Both mention debug
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway
-
v2.1.228
Gateway runs without an OIDC block, and names two more upstream failures
Both mention gateway