{"version":"2.1.310","anchor":"task-progress-events-without-a-summary-can-be-skipped-in-out","canonical_anchor":"task-progress-events-without-a-summary-can-be-skipped-in-out","heading":"Progress updates with no summary can be left out of streamed output","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/task-progress-events-without-a-summary-can-be-skipped-in-out","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Progress updates with no summary can be left out of streamed output\n\nClaude Code can now skip task progress events that carry neither a summary nor workflow progress when it writes its output stream\n\n**Unclear.** It is not clear whether this skipping is on by default or only when a program asks for it.\n\n**What**\n\nWhen Claude Code streams its events to a program reading them, for example through the SDK (the kit developers use to drive Claude Code from their own code), it can now leave out task progress events that have neither a summary nor any workflow progress attached. Events that do carry one of those are still written.\n\n**Why**\n\nPlain progress events with nothing in them add noise to the stream. Programs that read the stream may see fewer of them.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}