Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.260 ·

Background session runner gains an onMaxLifetime lifecycle hook

A hook can now override whether a background session gets killed at its max lifetime.

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaSessionswhat it touches
KindInternal Changesin v2.1.260,
Group of 2 Under the hood No documentation found

A hook can now override whether a background session gets killed at its max lifetime.

The child-process session manager (mr/Sr) constructor now accepts onMaxLifetime and onTerminating callbacks, and the created instance is stored on a ref (St.current) so other code can reach the active runner session, e.g. to check terminationRequested. The background-session runner's max-lifetime timeout now calls the onMaxLifetime hook to decide whether to wait or kill the child process, instead of always killing unless a turn is in flight; hook errors fall back to the previous default behavior. The background-result follow-up clear callback also now reports whether termination was requested (B?.(!1, k || St.current?.terminationRequested === !0)).

Read from
Names in the bundleonMaxLifetime

See this entry in the whole of v2.1.260 →

Feedback