{"version":"2.1.247","anchor":"truncated-task-output-now-admits-when-the-full-text-was-not-","canonical_anchor":"truncated-task-output-now-admits-when-the-full-text-was-not-","heading":"Truncated task output now admits when the full text was not saved","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/truncated-task-output-now-admits-when-the-full-text-was-not-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Truncated task output now admits when the full text was not saved\n\nTruncated task output now admits when the full text couldn't be saved to file.\n\n**What**\n\nWhen Claude Code truncates a task's output, the footer used to promise the whole thing had been written to a file. If the writer is failing or has lost data, it now says the full output could not all be saved and that the file may be missing or incomplete.\n\n**Details**\n\n- A new cleanup path flushes the output writer and logs, at error level, how many characters were discarded unwritten.\n- The message is assembled at runtime from the writer's state; there is no flag.\n\n**Evidence**\n\n`The full output could not all be saved to`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}