Source Intelligence

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.223 Home All releases olderv2.1.222 v2.1.224newer

Stream close with a parked question can now abort the in-flight query

Not switched on
Useful2 Signal3
SDK Control

Closing input while a question is pending can cancel the running query, once a remote setting says so.

The abort-on-close callback is wired at the CLI entry point but only selected when the gate reads "interrupt"; the fallback is "off".

Feature flag
tengu_cinder_swift Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.223: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.223. It isn't a statement about your account. What a flag value here can and cannot tell you

What

When the input stream closes while can_use_tool requests for the parked-question tool are still pending, the pending request ids can now be collected and used to abort the current query with a shutdown reason.

Details
  • the control session gained an onStreamClosedWithParkedQuestion callback plus a setter, wired at the CLI entry point to abort the query
  • selected only when the gate resolves to the string "interrupt"
  • the in-source fallback is "off", which keeps the older preserve/no-op behaviour; real values come from remote config
Evidence

tengu_cinder_swift

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.223 →