{"version":"2.1.296","anchor":"resuming-agents-in-diskless-sessions-now-verifies-transcript","canonical_anchor":"resuming-agents-in-diskless-sessions-now-verifies-transcript","heading":"Resuming agents gives specific errors when their history is damaged","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/resuming-agents-in-diskless-sessions-now-verifies-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Resuming agents gives specific errors when their history is damaged\n\nResuming an agent now checks its transcript and fails with a specific message for each problem instead of a generic error\n\n**Unclear.** It is not clear which sessions count as diskless for the saved-settings check.\n\n**What**\n\nWhen you resume an agent, a helper that works on part of a task, Claude Code now checks its transcript more closely. The transcript is the agent's saved record of the conversation so far. Before, most problems ended in one generic error. Each of these now fails with its own message:\n\n- a transcript that is too large or malformed\n\n- a transcript saved in an encoded form\n\n- a missing saved-settings file in diskless sessions, ones that do not keep files on the local disk\n\n- part of the transcript missing compared with the stored copy\n\n- an agent type that no longer matches any known agent\n\nThe error for background agents being switched off now names the agent. When part of the transcript is missing, the message suggests starting a new agent if the work is still needed.\n\n**Why**\n\nA resumed agent now stops with a clear reason rather than carrying on from a partial history. That way it does not quietly lose track of earlier work.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}