{"version":"2.1.280","anchor":"shell-command-line-tail-parsing-now-tracks-whether-a-segment","canonical_anchor":"shell-command-line-tail-parsing-now-tracks-whether-a-segment","heading":"Shell command-line tail parsing now tracks whether a segment was reached via &&","tier":"internal","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/shell-command-line-tail-parsing-now-tracks-whether-a-segment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Shell command-line tail parsing now tracks whether a segment was reached via &&\n\nClaude Code now tracks whether a shell command segment was reached via && when parsing compound command lines\n\n**Unclear.** The finding does not say what feature or permission check consumes this new andGated flag, so the practical effect on user-visible behavior is unclear.\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThis 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.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}