{"version":"2.1.304","anchor":"headless-cloud-client-drops-non-startup-frames-when-a-launch","canonical_anchor":"headless-cloud-client-drops-non-startup-frames-when-a-launch","heading":"Startup-only cloud launches now keep their output to the startup result","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/headless-cloud-client-drops-non-startup-frames-when-a-launch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Startup-only cloud launches now keep their output to the startup result\n\nWhen a cloud launch is set to end on its startup result, Claude Code now drops all other output except control responses and startup failures\n\n**What**\n\nSome cloud launches are set to end as soon as Claude Code reports how its startup went. For those launches, Claude Code now drops any output line other than a control response or a line carrying `startup_failure_reason`. Before, output was dropped only once the output stream had closed. A debug log entry notes when a line is dropped for this reason.\n\n**Why**\n\nThe output of a launch that only reports its startup result stays clean, so a program reading it gets just the answer it is waiting for.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}