Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Claude Code can now record that a --max-turns limit may not be enforced

If the service does not confirm the --max-turns limit, Claude Code now marks the limit as lost and assumes none is enforced

Under the hood Internal Changes
JSON All of v2.1.285
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Headless ModeArea: what it touches
Internal ChangesKind: in v2.1.285,
Internal ChangesSection of the release
What

--max-turns caps how many turns a run can take. A turn is one round of Claude reading a message and replying.

Claude 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.

Why

A 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear in which runs this happens and where you would see it.
Anthropic's release notes agreeFixed CLAUDE_CODE_RESUME_INTERRUPTED_TURN re-running a turn that had ended at --max-turns

See this entry in the whole of v2.1.285 →

Feedback