You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.260,
ImprovementsSection of the release
The help text for --kill-session-after-min now clarifies what actually happens at the wall-clock deadline: a session that is idle, parked at a permission prompt, or still starting up is released (paused server-side and resumable) rather than killed. Only a session with a turn still running, or one where the server keeps declining the release, gets SIGTERMed at the hard cap.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged self-hosted runner --kill-session-after-min to release a session that is only waiting on its user (paused, resumable on the next…
