{"version":"2.1.285","anchor":"remote-session-max-turns-is-passed-to-cloud-sessions-and-i","canonical_anchor":"remote-session-max-turns-is-passed-to-cloud-sessions-and-i","heading":"Turn limits are now passed to cloud sessions","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/remote-session-max-turns-is-passed-to-cloud-sessions-and-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Turn limits are now passed to cloud sessions\n\nA --max-turns limit on a cloud headless run is now sent to the cloud session, and Claude Code records whether the limit was confirmed\n\n**Unclear.** Whether the cloud service actually enforces the turn limit is not known.\n\n**What**\n\nA headless run works without the interactive screen. When Claude Code creates one in the cloud, it now passes along the turn limit set with `--max-turns`. Before, the limit was not forwarded. Claude Code also records whether the cloud service confirmed the limit, and keeps that confirmation with the session.\n\nClaude Code now also reacts when the service reports that the session already exists.\n\n**Why**\n\nA turn limit you set on a cloud headless run can now reach the cloud service, which can then honour it and confirm it back.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}