Unclear It is not clear what the outputs link changes about how a file is judged.
The pass that re-reads tracked files that changed on disk can now use an outputs link when judging them. It does this only when two conditions hold:
- the changed-file check itself is on, through its server-side switch or
CLAUDE_CODE_SETTLE_TOUCHED_FILES - a new server-side switch,
tengu_mossy_thrush, is also on
With both on, the pass also counts how each file came out, including those settled through the outputs link, and reports the counts once it finishes.
This refines how changed files are re-read and adds reporting on the results, behind a switch that has not been rolled out. Setting CLAUDE_CODE_SETTLE_TOUCHED_FILES alone does not turn the new path on.
tengu_mossy_thrush 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.300: 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.
tengu_fallow_plover Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.300: 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.300. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear what the outputs link changes about how a file is judged.
New in this build: tengu_mossy_thrush