{"version":"2.1.321","anchor":"shell-parser-text-after-a-closing-is-flagged-as-not-check","canonical_anchor":"shell-parser-text-after-a-closing-is-flagged-as-not-check","heading":"Shell commands with text after a closing ] are now marked as uncheckable","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/shell-parser-text-after-a-closing-is-flagged-as-not-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Shell commands with text after a closing ] are now marked as uncheckable\n\nClaude Code now marks a shell test command with text after its closing ] as one it cannot check before it runs\n\n**Unclear.** It is not confirmed whether these commands now always ask for permission or how the note is shown to you.\n\n**What**\n\nBefore running a shell command, Claude Code reads it to work out what it will do. A test command is the kind written between `[` and `]`. When more text follows the closing `]`, Claude Code now records that it could not read the command properly and keeps that note with its reading. The message for this case is: \"Text after a closing ] in this command can't be checked before it runs\".\n\n**Why**\n\nClaude Code no longer treats such a command as fully understood. Expect it to ask for your permission before running one rather than approving it automatically.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}