claude-code - 💡(How to fix) Fix [DOCS] [additionalDirectories] Read/Edit tools denied on mapped network drives — fixed in v2.1.133

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/permissions

Section/Topic

"Manage permissions" or the additionalDirectories / --add-dir coverage in the permissions documentation

Current Documentation

No documentation currently explains that Read, Edit, and Write tools were previously denied on mapped network drives (UNC paths) passed via --add-dir or the SDK's additionalDirectories option. The changelog for v2.1.133 notes the fix:

Fixed Read/Write/Edit being denied on mapped network drives passed via --add-dir / SDK additionalDirectories

But the --add-dir CLI documentation and additionalDirectories settings documentation do not mention network drive support or its previous limitations:

From permissions.md (line 38):

acceptEdits: Automatically accepts file edits and common filesystem commands (mkdir, touch, mv, cp, etc.) for paths in the working directory or additionalDirectories

From settings.md (line 274):

additionalDirectories: Additional working directories for file access. Most .claude/ configuration is not discovered from these directories

From cli-reference.md (line 44):

--add-dir: Add additional working directories for Claude to read and edit files. Grants file access; most .claude/ configuration is not discovered from these directories. Validates each path exists as a directory

None of these pages mention mapped network drives, UNC paths, or the previous denial behavior.

What's Wrong or Missing?

A. No documentation of network drive behavior

The documentation never mentions that --add-dir and additionalDirectories could be used with mapped network drives (e.g., Z:\, \\server\share), nor that such paths were previously blocked for Read/Edit operations before v2.1.133.

B. No changelog entry cross-reference in docs

The permissions and settings pages that document --add-dir and additionalDirectories have no link or reference to the relevant changelog entry for v2.1.133 where this was fixed.

Suggested Improvement

Add a note to the --add-dir documentation in cli-reference.md and the additionalDirectories documentation in settings.md (cross-referenced from permissions.md) explaining:

Mapped network drives and UNC paths (e.g., Z:\, \\server\share) are supported via --add-dir and additionalDirectories. Prior to v2.1.133, Read/Edit/Write operations on such paths were denied; this was fixed in v2.1.133.

This can be added as a parenthetical note or a separate "Network paths" subsection under the --add-dir flag description and the additionalDirectories setting description.

Impact

High - Prevents users from using a feature

Additional Context

Changelog reference (v2.1.133):

Fixed Read/Write/Edit being denied on mapped network drives passed via --add-dir / SDK additionalDirectories

SDK reference (agent-sdk/typescript.md line 324):

{
name: "additionalDirectories",
type: "string[]",
default: "[]",
description: "Additional directories Claude can access"
}

Affected Pages:

Total scope: 4 pages affected (all need a note about network drive / UNC path support)