{"version":"2.1.287","anchor":"bash-too-complex-parse-reason-text-reworded","canonical_anchor":"bash-too-complex-parse-reason-text-reworded","heading":"Plainer wording when a shell command cannot be checked ahead of time","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/bash-too-complex-parse-reason-text-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plainer wording when a shell command cannot be checked ahead of time\n\nWhen Claude Code cannot check a shell command in advance, the reason now says that part of the command cannot be checked, not a technical syntax label\n\n**Unclear.** It is not settled where this reason is shown, though it is likely the permission prompt.\n\n**What**\n\nBefore running a shell command, Claude Code tries to read it and work out what it will do. When part of a command is too complex to read that way, the reason Claude Code gives now says \"Part of this command (...) cannot be checked in advance\". It used to say \"Contains shell syntax (...) that cannot be statically analyzed\" and name an internal type for the piece it could not read.\n\nCommands that fail to parse at all still give the reason \"Parse error\".\n\n**Why**\n\nIf you are asked to approve a complicated shell command, the explanation should be easier to understand.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}