You'll notice
Adding a network path as a working directory now errors with guidance, suggesting a mapped drive letter on Windows.
Adding a network path as a working directory now surfaces a dedicated error explaining that network paths can't be used this way. On Windows, the error suggests mapping the share to a drive letter and using --add-dir instead.
Names in the bundle--add-dir
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.
Added since
A small documentation edit on Orchestrate teams of Claude Code sessions touched a line naming --add-dir after this was published.
For a teammate it brings back, Claude Code re-applies a definition that came from a project's `.claude/agents/` directory or an `--add-dir` directory only if you've [trusted the folder the agent file is in](/docs/en/permissions#what-runs-b…agent-teams see the edit
Confirmed since
Anthropic's documentation has since written up --add-dir, on CLI reference.
| `claude agents` | Open [agent view](/docs/en/agent-view) to monitor and dispatch parallel background sessions. Use `--cwd <path>` to show only sessions started under that directory, or `--json` to print active sessions as a JSON array fo…cli-reference see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --add-dir, on CLI reference.
Anthropic's release notes agree
Fixed /add-dir rejecting a directory inside the current working directory; it now loads that directory's skills, commands, and agents like…