{"version":"2.1.295","anchor":"headless-input-stream-gains-a-set-aside-layer-interrupt-get","canonical_anchor":"headless-input-stream-gains-a-set-aside-layer-interrupt-get","heading":"Headless mode can set incoming requests aside, and interrupts gain options","tier":"internal","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/headless-input-stream-gains-a-set-aside-layer-interrupt-get","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Headless mode can set incoming requests aside, and interrupts gain options\n\nIn headless mode, Claude Code now reads input through a layer that can hold requests aside, and interrupt handling gained options\n\n**Unclear.** It is not stated how interrupting or sending a message behaves differently as a result.\n\n**What**\n\nHeadless mode runs Claude Code without its interactive screen, as the Agent SDK and remote sessions do. In that mode, Claude Code now reads incoming input through a new layer that can set some requests aside instead of handling them at once. Interrupt handling, which runs when work is stopped partway, also gained new options, and there is a new step for when a person stops the work.\n\n**Why**\n\nThis affects how interrupting and sending a message straight away behave in SDK and remote sessions.\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}