{"version":"2.1.304","anchor":"cloud-attach-failed-start-emits-a-startup-result-and-a-sta","canonical_anchor":"cloud-attach-failed-start-emits-a-startup-result-and-a-sta","heading":"A cloud session that fails to start can now report it was refused","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/cloud-attach-failed-start-emits-a-startup-result-and-a-sta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### A cloud session that fails to start can now report it was refused\n\nWhen a cloud session fails to start for a stated reason, Claude Code can now send a startup result and end it as `start_refused`\n\n**Unclear.** The condition that decides between `start_refused` and `open_failed` is not stated.\n\n**What**\n\nWhen attaching to a cloud session fails at the start, Claude Code can now record a reason. In some cases with a reason, it sends a startup result message and ends the session as `start_refused`. Otherwise it ends it as `open_failed`, as before.\n\n**Why**\n\nThis changes how programs driving Claude Code through the SDK learn that a cloud session did not start.\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"}