{"version":"2.1.290","anchor":"shell-parser-hardening","canonical_anchor":"shell-parser-hardening","heading":"Changes to how shell commands are read when checking permissions","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/shell-parser-hardening","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Changes to how shell commands are read when checking permissions\n\nThe shell command reader now splits words at non-ASCII characters, checks folder changes differently and drops some entries from its blocked-read list\n\n**Unclear.** The overall effect on which commands are asked about or allowed is not clear.\n\n**What**\n\nClaude Code reads each shell command to decide whether to ask your permission. Three parts of that reading changed:\n\n- Non-ASCII characters, such as accented letters and symbols outside basic English, now count as breaks between words.\n\n- The check for commands that change folder (`cd`) now takes wildcard patterns into account.\n\n- A group of entries was removed from the list of paths that are blocked from reading.\n\n**Why**\n\nThese changes could alter which commands trigger a permission prompt.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}