{"version":"2.1.318","anchor":"hosted-worker-telemetry-for-background-shell-limit-stops-and","canonical_anchor":"hosted-worker-telemetry-for-background-shell-limit-stops-and","heading":"Usage data on background shell commands stopped at their time limit on hosted workers","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/hosted-worker-telemetry-for-background-shell-limit-stops-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Usage data on background shell commands stopped at their time limit on hosted workers\n\nClaude Code now reports when a background shell command is stopped at its time limit, restarted, and what work follows\n\n**What**\n\nA background shell command is one Claude Code leaves running while it carries on. Claude Code now reports usage data in three cases:\n\n- a background shell command is stopped at its time limit\n\n- the same command is started again\n\n- what kind of work follows a heavy stop\n\nThe details are grouped into ranges, such as time limit, quiet time, kind of work and CPU time, instead of exact values. The restart report only runs on hosted workers (machines Anthropic runs sessions on) and for the bash shell. The report on work after a stop splits sessions into two halves using `CLAUDE_CODE_REMOTE_SESSION_ID`.\n\n**Why**\n\nThis measures how background shell time limits behave on hosted workers. Nothing changes for local use.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}