Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
When a tool's result is too large and gets "spilled" (truncated, with the rest only retrievable by re-running the tool), the telemetry for that event now records spilled_bytes: the size of the part that was cut off. This is reported alongside the existing flags that mark output as truncated.
Why
This gives better visibility into how much output is being dropped from large tool results, which is useful for diagnosing when important information may have been truncated away.
