{"version":"2.1.295","anchor":"cloud-session-status-failed-reason-and-pausedblocked","canonical_anchor":"cloud-session-status-failed-reason-and-pausedblocked","heading":"Cloud sessions now show why they failed to start, and paused sessions show as blocked","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-session-status-failed-reason-and-pausedblocked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Cloud sessions now show why they failed to start, and paused sessions show as blocked\n\nCloud sessions that fail to start now show a reason, and paused sessions waiting on you show as blocked instead of working\n\n**What**\n\nClaude Code has changed how it reports the state of a cloud session, which is a session running on a remote machine rather than on your own computer.\n\n- **Startup failures:** when the cloud environment fails to start, the session now shows a trimmed reason for the failure. If no reason is available, it shows the text \"the cloud environment failed to start\". The previous code for this case did not work correctly.\n\n- **Paused sessions:** a session that is waiting for you to act and is also paused now shows as blocked. Before, any session waiting for you to act showed as working.\n\n**Why**\n\nThe list of agents and sessions now tells you what is actually happening. A failed start comes with a reason, and a paused session no longer looks as if it is still busy.\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"}