Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.299 ·

Self-hosted runner sessions are no longer kept alive by output from child processes

On self-hosted runners, output from child processes no longer restarts the startup idle timer once startup is over

You'll notice Bug Fixes
JSON All of v2.1.299
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
Bug FixesKind: in v2.1.299,
Bug FixesSection of the release
What

A 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.

Why

Programs 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.

See this entry in the whole of v2.1.299 →

Feedback