Background output that couldn't be written to disk now shows a visible gap marker instead of silently truncating.
What's wrong with this entry?
When 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.
- 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.
- 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.
[output omitted: it could not be written to disk]
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task