{"version":"2.1.236","anchor":"cloud-session-model-changes-are-announced-rather-than-prompt","canonical_anchor":"cloud-session-model-changes-are-announced-rather-than-prompt","heading":"Cloud-session model changes are announced rather than prompting","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/cloud-session-model-changes-are-announced-rather-than-prompt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Cloud-session model changes are announced rather than prompting\n\nA cloud session changing model now just notifies you instead of opening a local prompt.\n\n**What**\n\nWhen a cloud session changes model, you now get a notification instead of the local model-change flow being attempted: either \"The cloud session reset its model to the workspace default\" or a message naming the model it switched to.\n\n**Details**\n\n- Only applies on the remote thin-client path; local sessions keep the existing flow.\n- The consent path for the newer model now latches a marker so the error and consent branches cannot both fire for one switch.\n\n**Evidence**\n\n`The cloud session reset its model to the workspace default`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}