Sandbox allowRead Setting / Claude Code v2.1.77

What

New allowRead setting lets administrators re-allow specific read paths within broad denyRead regions, and a new allowManagedReadPathsOnly flag restricts reads to only policy-approved paths.

Details

allowRead: array of paths that take precedence over denyRead, enabling fine-grained "deny broad, allow narrow" patterns
allowManagedReadPathsOnly: boolean in policySettings.sandbox.filesystem — when true, only managed allowRead paths are permitted
Glob expansion supported for allowRead patterns
Logging for re-allowed paths within denied regions

Evidence

Settings schema (search for "Paths to re-allow reading within denied regions") and policy check (search for "allowManagedReadPathsOnly")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeAdded allowRead sandbox filesystem setting to re-allow read access within denyRead regions

See this entry in the whole of v2.1.77 →

The build it came inv2.1.77

16 Mar 2026 · 21 entries, this one is #4.

Either side of it

v2.1.76Older
v2.1.78Newer

Open the release →

Names in this entry

settingallowRead
The runner can warn about or block repo-committed settings that grant access outside the workspace.
settingdenyRead
Under a relaxed sandbox filesystem policy, the outside-reads block does nothing and this is now logged.

Anthropic's note

Upstream's own release notes for v2.1.77 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Added allowRead sandbox filesystem setting to re-allow read access within denyRead regions

Is this right?