{"version":"2.1.290","anchor":"bashphp-safety-messages-shortened-read-permission-check-si","canonical_anchor":"bashphp-safety-messages-shortened-read-permission-check-si","heading":"Shorter reasons shown for risky shell and PHP commands","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bashphp-safety-messages-shortened-read-permission-check-si","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shorter reasons shown for risky shell and PHP commands\n\nSome reasons Claude Code gives for flagging a shell command are shorter, including the one for risky PHP options\n\n**Unclear.** It is not confirmed whether the restricted-mode handling in the file-reading check was moved elsewhere or removed.\n\n**What**\n\nWhen Claude Code flags a shell command as possibly unsafe, it gives a reason. Some of those reasons are now shorter:\n\n- the PHP one now reads \"it runs php with -z, -c or a -d setting that loads a file\", without the list of example settings or the detail about where the file is\n\n- the one for the `${ \u2026@P }` form of shell expansion no longer includes its explanation\n\nThe check that decides whether a file may be read also changed: a separate branch for restricted mode was replaced by a single shared step.\n\n**Why**\n\nThe wording you see on these permission prompts is different.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}