{"version":"2.1.311","anchor":"per-turn-streaming-cpu-and-wall-time-telemetry","canonical_anchor":"per-turn-streaming-cpu-and-wall-time-telemetry","heading":"Turn results can report CPU and time spent streaming replies","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/per-turn-streaming-cpu-and-wall-time-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Turn results can report CPU and time spent streaming replies\n\nTurn results can now carry internal figures on CPU time, elapsed time and stream counts while replies stream in, sent only by certain workers\n\n**What**\n\nWhen Claude Code finishes a turn (one round of you asking and Claude replying), it produces a result record. That record can now include optional figures about streaming, the process of receiving Claude's reply piece by piece:\n\n- `process_cpu_ms_streaming`, the processor time used while streaming\n\n- `process_wall_ms_streaming`, the clock time spent streaming\n\n- `main_stream_count`, `main_stream_event_count` and `main_stream_chunk_count`, counts of the streams and their parts in the main conversation\n\nThese fields are marked internal. Only certain workers send them, and only when an internal check passes.\n\n**Why**\n\nThese are performance measurements. They do not change how Claude Code behaves for you.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}