{"version":"2.1.299","anchor":"self-hosted-runner-ignore-child-output-restarting-the-start","canonical_anchor":"self-hosted-runner-ignore-child-output-restarting-the-start","heading":"Self-hosted runner sessions are no longer kept alive by output from child processes","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/self-hosted-runner-ignore-child-output-restarting-the-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Self-hosted runner sessions are no longer kept alive by output from child processes\n\nOn self-hosted runners, output from child processes no longer restarts the startup idle timer once startup is over\n\n**What**\n\nA self-hosted runner is a machine you run yourself that hosts Claude Code sessions. It keeps an idle timer and stops sessions that have been idle too long. Activity counted as \"startup\" used to restart that timer every time, including output from programs the session started. Once startup is over, that activity is now ignored. The first such restart caused by child output is logged, and later ones are only written to the debug log.\n\n**Why**\n\nPrograms that print a lot could keep a session alive forever. Idle sessions on your runner should now shut down as expected, and the logs are less noisy.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}