{"version":"2.1.321","anchor":"cloud-gateway-failures-login-ended-cause-and-url-handling","canonical_anchor":"cloud-gateway-failures-login-ended-cause-and-url-handling","heading":"Cloud session failures can now report that the login ended","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/cloud-gateway-failures-login-ended-cause-and-url-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Cloud session failures can now report that the login ended\n\nFailures in cloud sessions can now be reported with the cause `login_ended`, and cloud gateway messages build their link differently\n\n**What**\n\nWhen a cloud session fails, Claude Code can now give `login_ended` as the cause. This cause also carries a marker saying whether the feature was switched off. Error messages about the cloud gateway, the service that connects cloud sessions, now work out their web address in a different way.\n\n**Why**\n\nThis adds a separate failure category for cloud sessions, so a session that stops because its login ended can be told apart from other failures.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}