Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.224 Home All releases ←olderv2.1.223 v2.1.225newer→
Claude Code v2.1.224

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

Use it now
Useful3 Signal3
Self-Hosted Runner Notable not in their notes

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

--retire-atSELF_HOSTED_RUNNER_RETIRE_AT--release-idle-session-min--startup-timeout-min--kill-session-after-min
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.224 →