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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Hook execution details are written to the debug log file. Start Claude Code with `claude --debug-file <path>` to write the log to a known location, or run `claude --debug` and read the log at `~/.claude/debug/<session-id>.txt`. The `--debu…hooks see the edit
* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de…channels-reference see the edit
A small documentation edit on Channels reference touched a line naming --debug after this was published.