Bash commands too complicated to analyze are now blocked outright when reads are locked to the working directory
When the permissions.blockReadsOutsideWorkingDirectories setting is turned on (which makes Claude Code's file tools refuse reads outside the working directory), Bash commands that are too structurally complex for Claude Code to analyze are now refused outright with a hard "ask" prompt, unless a specific exemption applies. Previously, these overly complex commands fell through to the normal complexity-based approval flow instead.
Commands too complex to analyze can't be reliably checked against the read-location block, so Claude Code now asks for explicit approval on them rather than risking one slipping through unchecked.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
When you set it in a project's `.claude/settings.json` or `.claude/settings.local.json`, Claude Code honors it under the same [workspace trust rule as hooks in settings files](/docs/en/permissions#what-runs-before-you-trust-a-folder). Whil…memory see the edit
A small documentation edit on How Claude remembers your project touched a line naming blockReadsOutsideWorkingDirectories after this was…
Fixed Bash commands the permission checker cannot fully analyze skipping the prompt under permissions.blockReadsOutsideWorkingDirectories…