{"version":"2.1.285","anchor":"max-turns-reported-as-lost","canonical_anchor":"max-turns-reported-as-lost","heading":"Claude Code can now record that a --max-turns limit may not be enforced","tier":"internal","area":"Headless Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/max-turns-reported-as-lost","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Claude Code can now record that a --max-turns limit may not be enforced\n\nIf the service does not confirm the `--max-turns` limit, Claude Code now marks the limit as lost and assumes none is enforced\n\n**Unclear.** It is unclear in which runs this happens and where you would see it.\n\n**What**\n\n`--max-turns` caps how many turns a run can take. A turn is one round of Claude reading a message and replying.\n\nClaude Code can now mark this option as lost. The reason it records is that the service did not confirm the turn limit, so it assumes no limit is being enforced.\n\n**Why**\n\nA run you started with `--max-turns` may not actually stop at that number. Don't rely on the limit alone when it hasn't been confirmed.\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}