{"version":"2.1.281","anchor":"cloud-session-the-permission-mode-chip-is-now-tracked-per-r","canonical_anchor":"cloud-session-the-permission-mode-chip-is-now-tracked-per-r","heading":"Cloud session: the permission-mode chip is now tracked per remote session and per screen","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-session-the-permission-mode-chip-is-now-tracked-per-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud session: the permission-mode chip is now tracked per remote session and per screen\n\nThe permission-mode chip for cloud sessions now keeps separate state per session, surviving screen changes and reattaching\n\n**What**\n\nWhen you work with a cloud session, a chip shows its permission mode (how freely Claude may act without asking). The chip's state used to be shared across the whole app. It now keeps separate state for each cloud session, tracking:\n\n- which screen it is on\n\n- the current mode and where it came from (you or the cloud)\n\n- a change still in flight\n\n- the last change applied\n\nIf the previous mode can no longer be used, the chip falls back to default. The notice that the cloud session could not be reached and the mode may be out of sync (shift+tab to retry) can now appear in one more situation.\n\n**Why**\n\nA mode change you made just before switching screens or reattaching to a session is now shown correctly instead of being lost or mixed up with another session.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}