{"version":"2.1.224","anchor":"cloud-sessions-can-be-created-through-a-newer-request-shape","canonical_anchor":"cloud-sessions-can-be-created-through-a-newer-request-shape","heading":"Cloud sessions can be created through a newer request shape","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cloud-sessions-can-be-created-through-a-newer-request-shape","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Cloud sessions can be created through a newer request shape\n\nCloud session creation can use a newer request shape for review and plan sources.\n\n**What**\n\nCreating a cloud session can now build a different request body for the newer session-create endpoint, carrying worker, source, outcome, seed bundle and branch-reuse fields in place of the older single session-context blob. It applies only when an account-level check passes and the session comes from ultrareview or ultraplan; nothing in this build sets that check, so what accounts get is decided elsewhere. `--project` and agent dispatch still refuse outright on accounts still using the old endpoint.\n\n**Evidence**\n\n`v1alpha2`\n\n- Area: Cloud Sessions\n- Names: `--project`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}