{"version":"2.1.311","anchor":"optional-garbage-collection-and-process-tuning-telemetry-on","canonical_anchor":"result-messages-can-carry-gc-and-process-tuning-telemetry-o","heading":"Cloud workers report new process startup and memory diagnostics","tier":"use","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/optional-garbage-collection-and-process-tuning-telemetry-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Cloud workers report new process startup and memory diagnostics\n\nAnthropic-hosted cloud workers can report startup timing, process tuning and, by opt-in, garbage-collection counts on session results\n\n**What**\n\nWhen Claude Code runs on Anthropic's cloud machines, it can now report more about how its process starts and uses memory.\n\n- Result messages, the summary sent at the end of a run, can carry `process_start_tuning`, `process_start_purge_delay_ms` and `process_garbage_collections`.\n\n- Garbage-collection counts, how often memory is cleaned up, are reported only when `CLAUDE_CODE_COUNT_GARBAGE_COLLECTIONS=1` was set at process start. They come only from Anthropic-hosted cloud workers with telemetry on, and never from a process hosting other sessions.\n\n- The tuning value records which Bun and mimalloc variables were set, never their values.\n\n- For `CLAUDE_CODE_REMOTE` sessions, CPU, elapsed time, page faults and storage reads are sampled between startup milestones (spare loaded, claim, input ready, first message, first turn) and sent as `process_stretches`. Per-phase startup timings are also reported.\n\n**Why**\n\nThese are diagnostics for Anthropic's cloud workers. They do not change how Claude Code behaves on your own computer, and the garbage-collection count stays off unless that variable is set.\n\n- Area: Telemetry\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}