{"version":"2.1.285","anchor":"max-turns-error-now-shows-the-turn-count","canonical_anchor":"max-turns-error-now-shows-the-turn-count","heading":"The max-turns error now shows which turn limit was reached","tier":"notice","area":"Headless Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/max-turns-error-now-shows-the-turn-count","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### The max-turns error now shows which turn limit was reached\n\nWhen a run stops at its turn limit, the error now reads \"Error: Reached max turns (N)\" with the limit in brackets\n\n**What**\n\nA turn is one round of Claude Code working on your request. When a run stops because it has reached its maximum number of turns, the result label now includes that number, for example \"Error: Reached max turns (25)\". It used to read only \"Error: Reached max turns\". If Claude Code cannot work out the number, it shows the old text without it.\n\n**Why**\n\nWhen you hit the limit, you can see straight away which limit applied, which helps if you set different limits in different places.\n\n- Area: Headless Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}