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 ·

Turn limits are checked for cloud sessions and ignored when attaching

A turn limit for a cloud session must be a whole number from 1 to 2147483647, and attaching to an existing session keeps that session's own limit

You'll notice Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What

A session is one continuous conversation with Claude Code. A turn limit is the most rounds of work it may do before it stops. Claude Code now checks the turn limit you give in two cases:

  • Cloud sessions: the limit must be a whole number from 1 to 2147483647.
  • Attaching to a session that already exists: the session keeps the turn limit it was created with, if it had one, and any limit you pass when attaching is not enforced. Claude Code tells you this.
Why

It makes clear that a turn limit such as --max-turns does nothing when you attach to a session that is already running, so you are not left thinking a new limit applies.

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 not clear which command or interface these checks belong to.
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