{"version":"2.1.299","anchor":"turn-timing-now-records-memory-and-cpu-between-turns-remote","canonical_anchor":"turn-timing-now-records-memory-and-cpu-between-turns-remote","heading":"Cloud sessions now record memory and CPU use around each turn","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/turn-timing-now-records-memory-and-cpu-between-turns-remote","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Cloud sessions now record memory and CPU use around each turn\n\nClaude Code now records memory use and between-turn CPU and wall time in its turn timing data for remote sessions on Linux\n\n**What**\n\nA turn is one round of you sending a message and Claude answering. Claude Code keeps a timing record for each turn. In remote sessions, meaning sessions that run on a machine in the cloud rather than on your own computer, that record now holds more:\n\n- Memory figures read from Linux at the start of a turn and again when the turn's output is consumed\n\n- CPU time and wall-clock time spent between turns\n\nBefore, only resource figures from the start of a turn were captured. This applies only on Linux, and only when `CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE` is not set to `self_hosted`. Nothing you see on screen changes.\n\n**Why**\n\nThis is usage data only. It shows that memory and CPU use in cloud sessions are now being measured.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}