{"version":"2.1.285","anchor":"max-turns-passed-through-to-a-request","canonical_anchor":"max-turns-passed-through-to-a-request","heading":"A turn limit is now passed along with a request when one is set","tier":"internal","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/max-turns-passed-through-to-a-request","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### A turn limit is now passed along with a request when one is set\n\nWhen a `maxTurns` turn limit is set, Claude Code now sends it along with a request instead of leaving it out\n\n**Unclear.** Which request now carries the turn limit is not settled.\n\n**What**\n\nA turn is one round of Claude responding and acting. When a `maxTurns` limit on the number of turns is set, Claude Code now includes it in a request it sends. When no limit is set, nothing extra is sent.\n\n**Why**\n\nA turn limit you set is more likely to be respected by the work carried out on the other end of that request, which may include remote sessions.\n\n- Area: Cloud Sessions\n- Names: `maxTurns`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}