{"version":"2.1.323","anchor":"headless-failed-start-with-stopped-flag-ends-session-cleanl","canonical_anchor":"headless-failed-start-with-stopped-flag-ends-session-cleanl","heading":"Headless sessions that fail to start and are stopped now end cleanly","tier":"notice","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/headless-failed-start-with-stopped-flag-ends-session-cleanl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Headless sessions that fail to start and are stopped now end cleanly\n\nA headless session whose startup fails and is stopped now ends as if its input closed, instead of continuing despite the failure\n\n**What**\n\nA headless session is one that runs without an interactive screen, for example in a script or in the cloud. Before, every failed startup took the path that lets the session continue despite the failure. Now, when startup has failed and has also been stopped, the session ends cleanly in the same way as when its input runs out.\n\nUnder one further condition, Claude Code also skips waiting for MCP servers, its connected outside tools, before the first turn.\n\n**Why**\n\nThis changes how headless and cloud sessions shut down when startup fails.\n\n- Area: Headless Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}