{"version":"2.1.314","anchor":"shell-parser-handles-case-esac-differently","canonical_anchor":"shell-parser-handles-case-esac-differently","heading":"Shell command parsing handles case statements differently","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/shell-parser-handles-case-esac-differently","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Shell command parsing handles case statements differently\n\nClaude Code's shell command reader changes how it handles the end of a case statement\n\n**Unclear.** Nothing shows what the extra condition does to how these commands are judged.\n\n**What**\n\nClaude Code reads shell commands before running them. In bash, a case statement picks between several options and ends with the word `esac`. The step that handles `esac` now has an extra condition, so some commands with case statements may be read differently than before.\n\n**Why**\n\nThis reading feeds into the permission and safety checks on shell commands. Commands that use case statements might be judged differently.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}