{"version":"2.1.295","anchor":"cloud-session-creation-checks-consolidated-into-one-restrict","canonical_anchor":"cloud-session-creation-checks-consolidated-into-one-restrict","heading":"Refusals to create cloud sessions now come from one combined check","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-session-creation-checks-consolidated-into-one-restrict","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Refusals to create cloud sessions now come from one combined check\n\nCreating a cloud session is now refused by a single check that gives its own message and reason, replacing two separate checks\n\n**Unclear.** It is not clear whether setting `CLAUDE_CODE_EVAL_CONFINED` still stops a cloud session from being created.\n\n**What**\n\nBefore, two separate checks could stop Claude Code from creating a cloud session:\n\n- A check for a restricted session, reported as \"restricted_session\"\n\n- A check for `CLAUDE_CODE_EVAL_CONFINED`, reported as \"eval_confined\"\n\nBoth are gone. A single check now decides, and when it refuses, it gives a message and a reason that are passed on to whatever reports the failure.\n\n**Why**\n\nThe message and reason you see when a cloud session is refused may be different from before.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}