{"version":"2.1.285","anchor":"maxturns-validation-for-cloud-sessions-and-attach","canonical_anchor":"maxturns-validation-for-cloud-sessions-and-attach","heading":"Turn limits are checked for cloud sessions and ignored when attaching","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/maxturns-validation-for-cloud-sessions-and-attach","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Turn limits are checked for cloud sessions and ignored when attaching\n\nA 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\n\n**Unclear.** It is not clear which command or interface these checks belong to.\n\n**What**\n\nA 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:\n\n- Cloud sessions: the limit must be a whole number from 1 to 2147483647.\n\n- 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.\n\n**Why**\n\nIt 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.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}