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.235 Home All releases ←olderv2.1.234 v2.1.236newer→
Claude Code v2.1.235

Chat loop loading and abort state consolidated into one turn object

Under the hood
Useful1 Signal1
Elsewhere

The chat loop's loading flags, abort controller and completion timestamp are now one turn object.

What

The scattered loading flags, abort controller and query-completion timestamp in the main chat loop are now members of a single turn handle passed around instead of separate props.

Details
  • Replaced: queryGuard, setIsLoading, setAbortController, abortController and the completion-timestamp state.
  • The turn handle exposes setAbortController, setExternalLoading, isExternalLoading, abortController, markQueryComplete, resetTiming and guard; the standalone setAbortController prop was removed from the REPL context.
  • Input handlers, background-session and background-query hooks, and the interrupt path all take the turn object.
  • The pending message queue moved onto the session as getCommandQueue, clearCommandQueue, recheckCommandQueue and enqueuePendingNotification.
Evidence

markQueryComplete, setAbortController

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