{"version":"2.1.281","anchor":"sessions-without-disk-writes-stop-capturing-oversized-comman","canonical_anchor":"sessions-without-disk-writes-stop-capturing-oversized-comman","heading":"Diskless sessions no longer write command output to files","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/sessions-without-disk-writes-stop-capturing-oversized-comman","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Diskless sessions no longer write command output to files\n\nIn diskless sessions, oversized command output is cut off instead of saved to a file, and Claude is not told to read output files\n\n**Unclear.** The finding does not say how a session is launched in diskless mode.\n\n**What**\n\nSome sessions are launched with a diskless option (`host.launchOptions.diskless()`), meaning the session writes no files. Task output is the text produced by commands and background tasks. Its handling now respects this option in two places:\n\n- The `TaskOutput` buffer assigns no output file path in a diskless session. When output passes the in-memory limit, later output is dropped instead of being written to a spill file on disk, and the reader gets the notice \"later output was discarded because this session writes no files.\" Before, a spill file was always created once the limit was exceeded.\n\n- The check that sets `outputFileReadable` for background task output (`CP(tools)`) now returns false first when the session is diskless. Before, it looked only at which tools were available. As a result, Claude is not told to read task output files in these sessions.\n\n**Why**\n\nDiskless sessions no longer try to write output files they are not allowed to create. The cost is that very long output from a command is cut off in these sessions, so expect truncation if you rely on the full output of a long-running command.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}