{"version":"2.1.285","anchor":"cloud-session-creation-sends-maxturns-and-builtintools-conf","canonical_anchor":"cloud-session-creation-sends-maxturns-and-builtintools-conf","heading":"Cloud sessions can now be started with a turn limit and a chosen set of tools","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/cloud-session-creation-sends-maxturns-and-builtintools-conf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Cloud sessions can now be started with a turn limit and a chosen set of tools\n\nStarting a cloud session can now send a turn limit and a list of built-in tools, and the server confirms the turn limit\n\n**Unclear.** It is not clear what sets the turn limit or when this newer interface is used.\n\n**What**\n\nA cloud session is a Claude Code conversation that runs on remote servers instead of on your machine. When Claude Code starts one through the newer version of the session-starting interface, it now also sends:\n\n- A maximum number of turns, where a turn is one round of Claude working and replying.\n\n- A list of the built-in tools the session may use.\n\nOnce the session is created, the server confirms whether it accepted the turn limit, and Claude Code reports progress when the session exists. If the list of built-in tools is empty, starting the session fails with the reason `builtin_tools_empty`. A failed start can now stop early.\n\n**Why**\n\nA turn limit on a cloud session is now passed to the server and confirmed, and not only kept on your side.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}