Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.260 ·

New env var to configure self-hosted runner session startup timeout

Runner session startup timeout can now be set via an environment variable too.

Use it now Improvements
JSON All of v2.1.260
Use it nowTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
ImprovementsKind: in v2.1.260,
What probably matters to youSection of the release

The startup-timeout idle-detection window for self-hosted runner session children can now be set via the SELF_HOSTED_RUNNER_STARTUP_TIMEOUT_MS environment variable, in addition to the existing --startup-timeout-min CLI flag.

Read from
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up SELF_HOSTED_RUNNER_STARTUP_TIMEOUT_MS, on Self-hosted environments reference. | `--startup-timeout-min <n>` | `SELF_HOSTED_RUNNER_STARTUP_TIMEOUT_MS` | `15` | Release a session slot if the child hasn't signaled that it initialized within N minutes of spawn. Cleared by the child's init signal on the [activity channel… self-hosted-environments-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up SELF_HOSTED_RUNNER_STARTUP_TIMEOUT_MS, on Self-hosted environments reference.

See this entry in the whole of v2.1.260 →

Feedback