{"version":"2.1.318","anchor":"stored-approvals-move-the-shell-with-a-permission-checked-cd","canonical_anchor":"stored-approvals-move-the-shell-with-a-permission-checked-cd","heading":"Stored approvals only change the shell's folder when permissions allow it","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/stored-approvals-move-the-shell-with-a-permission-checked-cd","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Stored approvals only change the shell's folder when permissions allow it\n\nBefore a stored approval runs, the shell moves to its folder only if that move passes the permission check\n\n**Unclear.** When stored approvals are used, and what you see when the folder change is refused, is not clear.\n\n**What**\n\nBefore a stored approval (a permission you gave earlier and that was saved) runs, Claude Code now moves the shell to the right folder with `cd`. That move only happens if it passes the permission check, through any of these:\n\n- a permission rule\n\n- the current permission mode\n\n- Bash's own safety checks\n\n- the classifier that judges commands\n\nIf none of them allows it, Claude Code logs a warning and leaves the shell in the folder it was in.\n\n**Why**\n\nThis keeps the folder change itself under the same permission rules as any other command, so a stored approval cannot move the shell somewhere you have not allowed.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}