{"version":"2.1.323","anchor":"stored-approval-cd-now-reports-failure-and-permits-tool-cont","canonical_anchor":"stored-approval-cd-now-reports-failure-and-permits-tool-cont","heading":"Restoring an approved folder now reports whether the shell moved there","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/stored-approval-cd-now-reports-failure-and-permits-tool-cont","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Restoring an approved folder now reports whether the shell moved there\n\nWhen Claude Code moves the shell back to a folder from a stored approval, it now reports whether that worked and accepts more kinds of approval\n\n**Unclear.** Which approvals count as coming from the tool container is not stated.\n\n**What**\n\nClaude Code can store permission approvals, and it can move the shell back into a folder it was approved for. When it does this, it now reports whether the move ended well. Before, it reported nothing.\n\nIt now also accepts an approval that comes from the tool container. Before, it accepted only approvals from rules, from the permission mode, from Bash and from the automatic classifier. If the move fails, the message now says the shell may not have moved.\n\n**Why**\n\nThis affects how folders tied to stored permissions are restored, and a failed restore is now reported.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}