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.224 ·

Runner lifecycle controls: scheduled retirement, idle release, outcome branch push

New flags retire a runner at a set time, release idle sessions, and control drain behaviour.

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

The runner gains a set of flags for managing how long it lives. --retire-at (or SELF_HOSTED_RUNNER_RETIRE_AT, an absolute Unix timestamp in seconds) releases active sessions, stops accepting new work and exits 0. --release-idle-session-min and --startup-timeout-min (default 15) are watchdogs, --kill-session-after-min waits for the current turn to finish first, and --drain-wait-sec sets drain time.

Details
  • --drain-wait-bg-tasks-sec is a deprecated alias for --drain-wait-sec.
  • --push-outcome-on-release pushes the session's tracked outcome branches to the source remote when a session ends without completing, and fetches them back if that session later resumes on a fresh worker.
  • Retirement releases sessions through the same path as idle release.
  • Release outcomes are reported through telemetry named self_hosted_release_session, with reasons including released_false_backstop.
Evidence

SELF_HOSTED_RUNNER_RETIRE_AT

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: SELF_HOSTED_RUNNER_RETIRE_AT

See this entry in the whole of v2.1.224 →

Feedback