{"version":"2.1.301","anchor":"new-cloud-cause-for-unapproved-sessions","canonical_anchor":"new-cloud-cause-for-unapproved-sessions","heading":"New 'cloud' outcome for sessions that are not yet approved","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/new-cloud-cause-for-unapproved-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### New 'cloud' outcome for sessions that are not yet approved\n\nAn unapproved session can now be given a third outcome, 'cloud', alongside the existing 'card' and 'review'\n\n**Unclear.** What the 'cloud' outcome checks for and what it does for the user are not stated.\n\n**What**\n\nWhen a session has not been approved, Claude Code works out a reason, which used to be either \"card\" or \"review\". There is now a third, \"cloud\", used when no served flag is present and a further check passes.\n\n**Why**\n\nThis adds a new way for an unapproved session to be routed.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}