{"version":"2.1.287","anchor":"cloud-session-start-up-now-refuses-to-serve-unless-it-was-re","canonical_anchor":"cloud-session-start-up-now-refuses-to-serve-unless-it-was-re","heading":"Cloud sessions now stop at start-up if they were not recognised as cloud launches","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-session-start-up-now-refuses-to-serve-unless-it-was-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cloud sessions now stop at start-up if they were not recognised as cloud launches\n\nA cloud session that was not recognised as a cloud launch at start-up now exits with an error before doing anything\n\n**Unclear.** It is not known what the start-up check examines or what normally marks a launch as a cloud one.\n\n**What**\n\nWhen Claude Code starts as a cloud session (a session running on a remote machine with no interactive screen), it now runs a check first. If the launch was not recognised as a cloud launch at start-up, Claude Code exits before serving anything and shows: \"this cloud session launch was admitted without being recognised as one at start-up, so it was stopped before it served anything. Please report this.\" Before, it went straight on to start serving.\n\n**Why**\n\nA cloud session launched by mistake now stops instead of running. If you see this error, the message asks you to report it.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}