{"version":"2.1.323","anchor":"bash-parser-flags-a-comment-inside-a-for-in-list","canonical_anchor":"bash-parser-flags-a-comment-inside-a-for-in-list","heading":"A # inside a shell for-loop list is now flagged","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-parser-flags-a-comment-inside-a-for-in-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A # inside a shell for-loop list is now flagged\n\nClaude Code now flags shell commands that put a # in the word list of a for ... in loop as possibly misread\n\n**Unclear.** It is not clear what happens to a flagged command, such as whether you are asked before it runs.\n\n**What**\n\nClaude Code reads shell commands before running them so it can check permissions. It now marks a command as possibly misread when a `#` appears in the list of words after `for ... in`.\n\n**Why**\n\nA `#` there can be read differently by Claude Code and by the shell, so the command is singled out for its permission checks.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}