{"version":"2.1.285","anchor":"cloud-session-flag-table-maxturns-no-longer-unsupported-de","canonical_anchor":"cloud-session-flag-table-maxturns-no-longer-unsupported-de","heading":"Turn limits are no longer listed as unsupported in cloud sessions","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/cloud-session-flag-table-maxturns-no-longer-unsupported-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Turn limits are no longer listed as unsupported in cloud sessions\n\nCloud sessions no longer flag a turn limit as unenforced, and the flag table for cloud sessions gains a desktop entry\n\n**Unclear.** It is not clear whether the cloud side actually enforces the turn limit, or what the new desktop entry does.\n\n**What**\n\nWhen you start a cloud session (a Claude Code session that runs on a remote machine instead of your own), Claude Code checks your command-line options against a table of options that cloud sessions do not support. The entry for the maximum number of turns, which used to say \"no turn limit is enforced in a cloud session yet\", has been removed from that table. The turn limit you set is now passed into the cloud session's settings. The same table also gains an entry for desktop.\n\n**Why**\n\nA turn limit set with `--max-turns` may now carry over to a cloud session instead of being reported as unsupported.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}