{"version":"2.1.281","anchor":"cloud-gateway-sign-in-and-settings-errors-reworded-for-sessi","canonical_anchor":"cloud-gateway-sign-in-and-settings-errors-reworded-for-sessi","heading":"Cloud gateway sign-in and settings errors reworded for sessions not running in your terminal","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-gateway-sign-in-and-settings-errors-reworded-for-sessi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud gateway sign-in and settings errors reworded for sessions not running in your terminal\n\nCloud gateway sign-in and availability errors now tell you to sign in from a terminal where the session runs, or to ask your admin\n\n**What**\n\nSome 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:\n\n- `401`: the gateway did not accept your sign-in.\n\n- `403`: the gateway refused access.\n\n- unavailable: the gateway could not be reached.\n\nThey 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.\n\n**Why**\n\nTelling 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."}