{"version":"2.1.281","anchor":"bash-safety-analysis-now-tracks-zshs-dirstack-after-pushdp","canonical_anchor":"bash-safety-analysis-now-tracks-zshs-dirstack-after-pushdp","heading":"Bash safety analysis now tracks zsh's dirstack after pushd\/popd","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bash-safety-analysis-now-tracks-zshs-dirstack-after-pushdp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bash safety analysis now tracks zsh's dirstack after pushd\/popd\n\nBash permission checks now track zsh's lowercase dirstack as well as DIRSTACK after pushd and popd\n\n**What**\n\nBefore running a shell command, Claude Code checks it without running it to decide whether to ask your permission. As part of that it tracks which shell variables a command changes. After `pushd` and `popd`, commands that move between folders and remember earlier ones, it now records both `DIRSTACK` and zsh's lowercase `dirstack` as changed. `dirstack` is also added to the list of special zsh variable names.\n\n**Why**\n\nIn practice, the permission check has a more accurate picture of what folder-stack commands change under zsh, a common shell."}