{"version":"2.1.301","anchor":"diskless-session-transcript-writes-drop-entries-explicitly-a","canonical_anchor":"diskless-session-transcript-writes-drop-entries-explicitly-a","heading":"Sessions without local disk storage drop transcript entries instead of writing them","tier":"notice","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/diskless-session-transcript-writes-drop-entries-explicitly-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Sessions without local disk storage drop transcript entries instead of writing them\n\nIn sessions with no local disk, transcript entries with nowhere to go are now dropped with an error, and metadata folders are no longer created\n\n**What**\n\nA transcript is the saved record of a session. Claude Code now handles sessions that have no local disk storage differently:\n\n- A transcript entry that arrives with no storage backend is dropped, and an error is reported: \"diskless session: transcript entry queued with no storage backend; entry dropped\".\n\n- Folders for agent metadata and remote agent metadata are not created.\n\n- Repairing a half-written end of a transcript file is skipped.\n\nIn any session, an entry whose agent ID cannot name a transcript file is now dropped with the log message \"appendEntry invariant: agentId cannot name a transcript file; entry dropped\" instead of being written.\n\n**Why**\n\nThis prepares Claude Code to run sessions that have no local disk, and it makes failed transcript writes show up as reported errors instead of happening silently.\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"}