{"version":"2.1.300","anchor":"headless-heap-census-telemetry-for-hosted-workers","canonical_anchor":"headless-heap-census-telemetry-for-hosted-workers","heading":"Hosted workers record memory snapshots when usage climbs","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/headless-heap-census-telemetry-for-hosted-workers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hosted workers record memory snapshots when usage climbs\n\nClaude Code running as a hosted worker now records a count of what fills its memory, at most three times, when memory use passes set limits\n\n**What**\n\nWhen Claude Code runs as a hosted worker, meaning a copy running on a server rather than on your own machine, it can now record a memory snapshot after a turn. A turn is one round of you sending a message and Claude answering. The snapshot counts how many objects of each type are in memory.\n\nA snapshot is taken when the process's memory use passes certain limits. The limits are worked out from one base size, which is 2048 MiB unless a server-side setting supplies a different number:\n\n- 4 times the base size\n\n- 2 times the base size\n\n- the base size itself\n\nAt most three snapshots are taken per session. This only runs for hosted workers.\n\n**Why**\n\nThis is diagnostic data about memory use in hosted sessions. It does not change anything you see or do.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}