{"version":"2.1.301","anchor":"diskless-sessions-refuse-direct-session-file-writes","canonical_anchor":"diskless-sessions-refuse-direct-session-file-writes","heading":"Sessions without local storage no longer write session files straight to disk","tier":"notice","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/diskless-sessions-refuse-direct-session-file-writes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Sessions without local storage no longer write session files straight to disk\n\nIn a session without local storage, Claude Code now refuses to write transcripts and other session files directly to disk\n\n**What**\n\nSome sessions run \"diskless\", meaning they have no local disk to keep their files on. In these sessions, Claude Code now refuses to write its own session files directly to disk. These include the conversation transcript, small side files and session details. It shows an error saying that it refused a direct write of a session file.\n\nSeveral places that read the transcript, or write to it when a session stops, now do nothing or return nothing in these sessions.\n\n**Why**\n\nRemote and cloud sessions keep their session data out of the local disk, so nothing is left behind there by accident.\n\n- Area: Diskless Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}