{"version":"2.1.295","anchor":"tool-results-file-writes-refused-when-session-keeps-no-local","canonical_anchor":"tool-results-file-writes-refused-when-session-keeps-no-local","heading":"Large tool results are not written to disk in sessions that keep no local files","tier":"notice","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/tool-results-file-writes-refused-when-session-keeps-no-local","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Large tool results are not written to disk in sessions that keep no local files\n\nSessions that keep no files on this machine now refuse to save tool results to disk instead of writing them\n\n**What**\n\nWhen a tool call produces a very large result, Claude Code can save it to a file on disk instead of keeping all of it in the conversation. A tool call is a single action Claude takes, such as running a command. In a session that keeps no files on the machine, Claude Code now refuses that write and reports \"tool-results file refused: this session keeps no files on this machine\".\n\n**Why**\n\nThis mainly matters for remote or short-lived sessions that would otherwise spill large results to disk. In those sessions the write now stops with a clear message.\n\n- Area: Diskless Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}