{"version":"2.1.247","anchor":"background-task-output-that-cannot-be-written-to-disk-is-now","canonical_anchor":"background-task-output-that-cannot-be-written-to-disk-is-now","heading":"Background task output that cannot be written to disk is now marked instead of vanishing","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/background-task-output-that-cannot-be-written-to-disk-is-now","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Background task output that cannot be written to disk is now marked instead of vanishing\n\nBackground output that couldn't be written to disk now shows a visible gap marker instead of silently truncating.\n\n**What**\n\nWhen Claude Code fails to write a background task's output to its on-disk buffer, it inserts a visible placeholder line so the transcript shows an explicit gap rather than text that just looks cut short.\n\n**Details**\n\n- The first write failure puts the marker at the front of the buffer and latches, so the note appears once rather than per failed write.\n- Once more than 16 MB of unwritten output has piled up, it logs at error level, discards the pending output and keeps only the marker.\n\n**Evidence**\n\n`[output omitted: it could not be written to disk]`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}