{"version":"2.1.302","anchor":"ultraplanmcp-task-keepdrive-option-and-headless-transcrip","canonical_anchor":"ultraplanmcp-task-keepdrive-option-and-headless-transcrip","heading":"Stored transcripts that cannot be fully read are now kept instead of treated as empty","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/ultraplanmcp-task-keepdrive-option-and-headless-transcrip","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Stored transcripts that cannot be fully read are now kept instead of treated as empty\n\nIn some cases Claude Code now reads a stored transcript to its end, and keeps it as a conversation if it cannot decide whether it is empty\n\n**What**\n\nClaude Code checks whether a stored transcript actually holds a conversation. A transcript is the saved record of a session. Before, it only looked at the records through its usual reader.\n\nIn some cases it now reads the stored transcript right to its end. If it still cannot tell, it logs a warning saying it could not read the transcript to its end and is keeping it as if it holds a conversation.\n\nSeparately, when an ultraplan or MCP task ends, Claude Code can now be told to keep the controller that stops the task running, rather than always clearing it.\n\n**Why**\n\nThis is a more careful check for empty transcripts in stored sessions. When in doubt, a transcript is kept rather than treated as empty.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}