{"version":"2.1.300","anchor":"headless-handbacks-stand-aside-gated-by-a-string-valued-fla","canonical_anchor":"headless-handbacks-stand-aside-gated-by-a-string-valued-fla","heading":"Headless sessions can handle handed-back messages separately once a stop is requested","tier":"internal","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/headless-handbacks-stand-aside-gated-by-a-string-valued-fla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Headless sessions can handle handed-back messages separately once a stop is requested\n\nIn headless sessions, handed-back messages can now stay out of follow-up batching after a stop, behind a server-side setting\n\n**What**\n\nA headless session is one where Claude Code runs without its interactive screen, for example when driven by another program. In these sessions, messages from other sessions wait in a queue, and some are handbacks, where work is passed back. When a stop has been requested, queued handbacks can now step out of the batch of follow-up messages instead of being grouped with them.\n\nThis only happens when a server-side setting is set to the value \"on\".\n\n**Why**\n\nThis changes the order in which messages are processed in headless and SDK sessions after a stop.\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}