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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Loop ticks must report whether anything happened

You'll notice
Useful2 Signal3
Background Tasks

Self-scheduled loops that do nothing now collapse quietly instead of scrolling filler past you.

What

A self-scheduled loop tick now has to tell the scheduler whether it changed anything, by passing a noop flag set true for a tick that did nothing. Quiet holds collapse in your terminal instead of scrolling past.

Details
  • Applies to the three continuation prompts used by self-scheduled (non-cron) loops; cron-driven loops are unchanged.
  • The scheduling tool already documented the flag: "Consecutive noop: true ticks are collapsed in the user's terminal view and tracked as a streak."
Evidence

and \noop\ set to \true\ if this tick changed nothing (or \false\ if it did)

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