A gated code path changes how Claude Code detects unresolved tool uses
The function that finds unresolved tool uses (findUnresolvedToolUse) now has a new code path controlled by a feature flag. When enabled, it uses a new lookup function combined with the existing check for the last assistant turn, instead of the previous lookup function it used before.
This appears to be a behind-the-scenes change to how Claude Code identifies tool calls that haven't been resolved yet, likely aimed at improving accuracy or performance of that detection.
The tengu_eager_pillow gate controlling this path has no recorded reading, so nothing can be said here about whether it's on or off.
tengu_eager_pillow Not enough to sayNothing 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.274: off
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.274. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Whether tengu_eager_pillow is enabled is unread and not established by this finding.
New in this build: tengu_eager_pillow