You'll notice
Useful2 Signal2
When background event batches get cut short, Claude is told how many events are still waiting.
What's wrong with this entry?
Anonymous. No account, no email.
What
When background events are delivered to Claude in batches, a batch cut short by size or count limits now says so in a system note, and each attachment carries a count of how many events are still waiting, so the model knows nothing was silently dropped.
Details
- Batches that hit the size or count limit append a "delivery chunked" note rather than ending mid-list with no signal.
- Cancelling the queue settles every undelivered event as dropped with the reason "interrupt cleared the queue", instead of leaving them unresolved.
- These event attachments are also now kept out of one transcript-collapsing path, so they stay visible in history.
Evidence
delivery chunked:
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