What probably matters to youSection of the release
Unclear It is not clear where the allowWithinDeny list comes from, or whether it is a setting you can write yourself.
What
The sandbox limits which files commands run by Claude can read or write. It now supports allowWithinDeny, a list of paths that stay allowed even though they sit inside a denied area.
Linux enforcement: on Linux and WSL, the sandbox keeps each allowWithinDeny path writable inside a folder whose writing is denied. Before, a write deny made everything beneath it read-only. If an entry cannot be kept writable, a message is logged.
Violation reports: the Linux monitor that reports sandbox breaches no longer flags writes to a path covered by an allowWithinDeny entry.
Permission dialog: a new dim line, "Allowed within denied:", lists these paths next to the existing deny-within-allow list.
Commit secrets prompt: the Bash prompt that warns about committing secrets now lists .claude/settings.local.json.
Why
You can block writes to a whole folder while keeping one narrow path inside it writable. The dialog shows these exceptions so you can check what the sandbox actually permits.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear where the `allowWithinDeny` list comes from, or whether it is a setting you can write yourself.
Anthropic's release notes agreeFixed .claude/settings.local.json not being ignored globally when the folder became a git repository later, or on a new machine
