{"version":"2.1.290","anchor":"shell-launch-refusal-reasons-reworded","canonical_anchor":"shell-launch-refusal-reasons-reworded","heading":"Shorter explanations when a shell launch is refused","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/shell-launch-refusal-reasons-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shorter explanations when a shell launch is refused\n\nThe reasons Claude Code gives for refusing to analyse certain shell launches are now shorter\n\n**Unclear.** Whether the way these shell launches are matched also changed is not settled.\n\n**What**\n\nWhen Claude Code cannot safely understand how a command starts a shell, it gives a reason. Those reasons are now shorter. For example, one now reads \"it runs bash with an rc file by a relative name\" instead of mentioning the launch directory.\n\n**Why**\n\nThe text changed, and this wording may appear in permission prompts.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}