{"version":"2.1.318","anchor":"cloud-session-dropped-queued-messages-notice-and-start-refu","canonical_anchor":"cloud-session-dropped-queued-messages-notice-and-start-refu","heading":"Cloud sessions explain when they are refused at start","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/cloud-session-dropped-queued-messages-notice-and-start-refu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Cloud sessions explain when they are refused at start\n\nCloud sessions that are refused at start now show a start_refused warning and explain that messages already sent are saved on the session\n\n**What**\n\nA cloud session is a Claude Code session that runs on a remote machine instead of your own. When the remote worker refuses to start one, Claude Code now treats that refusal as a failed start and tells you about it.\n\n- A new `start_refused` reason shows the message 'because the cloud session couldn't start. The next line says why.' Before this release only start-failed and disconnected messages existed.\n\n- A notice explains that anything already sent is saved: 'What you sent went out before the cloud session failed to start. It's stored on the session, so there's no need to send it again.'\n\n- The message that was waiting to be sent is dropped instead of being resent.\n\n- A small timer shows a short-lived banner.\n\n- The session link is now passed along when messages are converted, so they can include the session's URL and organisation id.\n\n**Why**\n\nA failed cloud start is now shown on screen instead of going unnoticed. You also learn that you do not need to send your message again, which avoids duplicate messages.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}