What
When Claude Code looks at a compound shell command (one with multiple parts joined by things like &&, ;, |, or newlines) to figure out the last meaningful segment, it now also records whether that segment was reached specifically through an && chain, as opposed to being separated by ;, |, or a newline. Previously this internal check only returned the segment text itself.
Why
This is an internal parsing detail rather than something a user directly configures, but it means Claude Code's handling of command lines (for example, when deciding how to treat or permission-check a command) can now distinguish &&-chained commands from other kinds of separators.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what feature or permission check consumes this new andGated flag, so the practical effect on user-visible behavior…