{"version":"2.1.260","anchor":"kill-session-after-min-clarified-idleprompt-parked-session","canonical_anchor":"kill-session-after-min-clarified-idleprompt-parked-session","heading":"kill-session-after-min clarified: idle\/prompt-parked sessions are released, not killed, at the cap","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/kill-session-after-min-clarified-idleprompt-parked-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### kill-session-after-min clarified: idle\/prompt-parked sessions are released, not killed, at the cap\n\n--kill-session-after-min now clarifies idle sessions are released and resumable, not killed.\n\nThe 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.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}