Some Claude Code sessions do not run in the terminal in front of you. For those sessions, three error messages about the Cloud gateway's managed settings have been reworded. Managed settings are settings an organisation pushes to everyone's Claude Code. The three errors are:
401: the gateway did not accept your sign-in.
403: the gateway refused access.
unavailable: the gateway could not be reached.
They now point you to a terminal where the session runs, or to your admin. One message reads: "Run claude in a terminal where this session runs, then sign in again with /login." The unavailable message is now picked from whole ready-written sentences. Before, it was pieced together from "Check your network connection, or" plus a second part.
Why
Telling someone to sign in again is not much help when the session is not in their own terminal. The new wording says where to run /login and who to ask when that is not possible.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded telemetry.resource_attributes to the Claude apps gateway config, to put fixed labels on the telemetry of Claude Desktop and /login…
