{"version":"2.1.309","anchor":"shell-variable-tracking-refuses-values-containing-a-marker","canonical_anchor":"shell-variable-tracking-refuses-values-containing-a-marker","heading":"Shell permission checks treat some variable values as unknown","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/shell-variable-tracking-refuses-values-containing-a-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Shell permission checks treat some variable values as unknown\n\nClaude Code's shell command checker now gives up on a variable whose value contains a particular marker\n\n**Unclear.** Which marker makes a variable's value count as unknown is not stated.\n\n**What**\n\nBefore running a shell command, Claude Code reads it to work out what it will do, including what values its variables hold. A variable here is a named value inside the command, such as a for-loop variable. If a variable's value contains a certain marker, Claude Code now treats that value as unknown instead of using it.\n\n**Why**\n\nThis makes the check stricter, so commands like this are less likely to be judged safe on a guess.\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"}