{"version":"2.1.317","anchor":"hosted-workers-watch-for-processes-left-running-after-a-bash","canonical_anchor":"hosted-workers-watch-for-processes-left-running-after-a-bash","heading":"Hosted cloud sessions now track programs left running after shell commands","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/hosted-workers-watch-for-processes-left-running-after-a-bash","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Hosted cloud sessions now track programs left running after shell commands\n\nHosted cloud sessions can now record programs still running after a shell command ends, without stopping them\n\n**What**\n\nWhen Claude Code runs as a hosted worker, meaning on Anthropic's cloud machines, it can now watch for groups of programs that are still running after a shell command finished, such as a development server. For each group it records:\n\n- CPU use\n\n- how long it has been running\n\n- whether it is listening for network connections\n\nThis only happens when `CLAUDE_CODE_DIAGNOSTICS_FILE` is set. Its limits come from a remote setting that is empty unless the server sends a value, and a malformed value is reported as invalid. It only watches and does not stop anything.\n\n**Why**\n\nThis lays the groundwork for spotting forgotten programs left running in cloud sessions. Nothing is stopped yet.\n\n- Flag `tengu_parallel_lantern`: Not enough to say (read for one account on one subscription tier against v2.1.317; 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: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}