{"version":"2.1.299","anchor":"new-process-memorycpu-telemetry-fields-on-results","canonical_anchor":"new-process-memorycpu-telemetry-fields-on-results","heading":"Anthropic-hosted sessions now report memory and CPU use per turn","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/new-process-memorycpu-telemetry-fields-on-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Anthropic-hosted sessions now report memory and CPU use per turn\n\nTurn results gain memory and CPU fields, sent only by Anthropic-hosted workers on Linux with telemetry on\n\n**What**\n\nAt the end of each turn (one round of request and reply), Claude Code sends a result message. That message can now carry figures about the Claude Code process itself, such as:\n\n- `process_rss_mib_turn_start` and `process_rss_mib_result`: memory in use at the start and end of the turn\n\n- `process_peak_rss_mib`: the highest memory use\n\n- `process_cpu_ms_turn`: processor time used during the turn\n\n- processor and clock time between turns, and `handoff_intake_phases_ms`\n\nThese are only sent by workers that Anthropic hosts, with telemetry (usage reporting) switched on, and only on Linux. Claude Code running on your own machine does not send them.\n\n**Why**\n\nThe figures let Anthropic watch how much memory and processor time hosted sessions use, for example to spot memory that keeps growing over a long session.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}