{"version":"2.1.311","anchor":"bash-command-parser-tightens-handling-of-array-assignments","canonical_anchor":"bash-command-parser-tightens-handling-of-array-assignments","heading":"Some unusual bash commands are now treated as unclear and may ask for permission","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bash-command-parser-tightens-handling-of-array-assignments","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Some unusual bash commands are now treated as unclear and may ask for permission\n\nClaude Code's bash reader now treats more ambiguous array and bracket forms as unclear, so some commands may ask for permission\n\n**What**\n\nBefore running a shell command, Claude Code reads it to work out whether it is simple and safe or needs your permission. That reader now treats more constructs as unclear, meaning different shells could read them differently. These include:\n\n- text straight after the `)` that closes an array assignment such as `name=( ... )`\n\n- a `[` in a word that is still open at a space, tab, line break or one of `; & | < > ( )`\n\n- an assignment such as `a[1]=(x)`\n\nIt also reads the value given to `ruby -F` in a special way when looking for which script a `ruby` command runs.\n\n**Why**\n\nThe permission check becomes more cautious. Some commands that used to be judged simple and run without asking may now ask for your permission.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}