{"version":"2.1.315","anchor":"idle-cpu-mark-telemetry-for-hosted-workers-driven-by-tengu","canonical_anchor":"idle-cpu-mark-telemetry-for-hosted-workers-driven-by-tengu","heading":"Idle CPU measurements for hosted cloud sessions","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/idle-cpu-mark-telemetry-for-hosted-workers-driven-by-tengu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Idle CPU measurements for hosted cloud sessions\n\nHosted cloud sessions can now record CPU use, open shells and listening network ports while idle, at set minute marks\n\n**What**\n\nWhen Claude Code runs as a hosted worker, meaning a session running on Anthropic's cloud machines rather than your own computer, it can now measure how busy the machine is while the session sits idle. It samples:\n\n- CPU use for the machine and for its resource group\n\n- open shells\n\n- listening network ports\n\nIt reports these at minute marks set by a remote configuration. This only happens when `CLAUDE_CODE_DIAGNOSTICS_FILE` is set. With no value sent from the server, the configuration is empty and nothing is measured.\n\n**Why**\n\nThis is internal measurement of how much load idle hosted sessions put on their machines. It does not run on your own computer.\n\n- Flag `tengu_starry_balloon`: Not enough to say (read for one account on one subscription tier against v2.1.315; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}