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.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Self-hosted runner waits for the turn that follows a background task

You'll notice
Useful3 Signal2
Self-Hosted Runner

A session still owing a report after a background task stays alive instead of being treated as idle.

What

A session whose background task has finished but which still owes one more turn to report the result now counts as waiting on you, so the runner keeps it alive instead of treating it as idle.

Details
  • Appears in the [runner:session] debug log as "finished background task awaiting the follow-up turn", next to the existing live-task and wakeup reasons.
  • Driven by a new callback the session uses to declare that a follow-up turn is pending.
Evidence

finished background task awaiting the follow-up turn

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.228 →