{"version":"2.1.295","anchor":"coordinator-bash-refusal-messages-now-give-the-reason-and-a","canonical_anchor":"coordinator-bash-refusal-messages-now-give-the-reason-and-a","heading":"Refused shell commands in coordinator mode now explain why","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/coordinator-bash-refusal-messages-now-give-the-reason-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Refused shell commands in coordinator mode now explain why\n\nIn coordinator mode, a refused shell command now comes with the reason it was refused and a hint about how to fix it\n\n**What**\n\nIn coordinator mode, Claude may only run shell commands that read things and change nothing. When Claude Code refuses a command for this reason, the message used to be the same fixed text every time. It now says why, for example:\n\n- which part of the command could not be confirmed as read-only\n\n- that a `cd` in the command is not needed\n\n- which word in the command caused the refusal\n\nThe message also reminds Claude that the shell still works and that a plain read-only command will still run.\n\n**Why**\n\nWith the reason in front of it, Claude can correct the command and carry on instead of giving up on the shell.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}