{"version":"2.1.292","anchor":"headless-print-loop-read-file-requests-drained-at-teardown","canonical_anchor":"headless-print-loop-read-file-requests-drained-at-teardown","heading":"Headless sessions can serve file reads and finish them before shutting down","tier":"internal","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/headless-print-loop-read-file-requests-drained-at-teardown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Headless sessions can serve file reads and finish them before shutting down\n\nHeadless sessions can handle file read requests from a host, and wait up to 30 seconds for pending ones before shutting down\n\n**Unclear.** It is not clear what sends these file read requests, or whether they are switched on for everyone.\n\n**What**\n\nA headless session is one that runs without the interactive screen, for example when another program drives Claude Code. Such a session can now answer requests to read files from its workspace, a few at a time.\n\nWhen the session shuts down, it now waits up to 30 seconds for any file read requests still in progress. Before, shutdown waited only for remote control operations and for session detach hooks, which are your own commands that run when a session detaches.\n\n**Why**\n\nA program driving the session can read files from its workspace, and a read that is still running when the session ends is no longer cut off.\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}