{"version":"2.1.296","anchor":"workflow-agent-spawn-environment-check-moved-and-wt-cal","canonical_anchor":"workflow-agent-spawn-environment-check-moved-and-wt-cal","heading":"Starting a remote session behaves differently when built-in tools are given","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/workflow-agent-spawn-environment-check-moved-and-wt-cal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Starting a remote session behaves differently when built-in tools are given\n\nStarting a remote session now names the session only when no built-in tools are given, after a check that can stop it\n\n**Unclear.** It is not clear what the new environment check refuses, or what a reader starting a remote session will notice.\n\n**What**\n\nClaude Code can start a session that runs remotely instead of on your own machine. Several steps in how that session is created have changed:\n\n- A title and branch name are now generated only when no list of built-in tools is supplied.\n\n- That step now runs after a check on the environment, and the check can stop creation early.\n\n- The list of built-in tools is no longer sent in one of the requests that creates the session.\n\n- A special way of handling one kind of creation failure has been removed.\n\n**Why**\n\nRemote sessions created with a list of built-in tools now take a different route.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}