{"version":"2.1.309","anchor":"bash-parser-glued-to-next-word-is-flagged-handlin","canonical_anchor":"bash-parser-glued-to-next-word-is-flagged-handlin","heading":"Bash commands with [ glued to the next word are now flagged","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/bash-parser-glued-to-next-word-is-flagged-handlin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Bash commands with `[` glued to the next word are now flagged\n\nClaude Code now flags a shell test written as `[` with no space after it, since that names a different command\n\n**What**\n\nIn shell scripts, `[` is a command that tests a condition and must be followed by a space. When Claude Code checks a Bash command and finds a test that starts with `[` with no space after it, it now reports \"[ glued to the next word names another command\". Without the space, the shell would look for a command with a different name.\n\nA separate fix changes how Claude Code reads commands that contain `))`.\n\n**Why**\n\nClaude Code checks commands more strictly before running them, so some Bash commands written this way may now be flagged or need you to approve them.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}