Skip to content
BENIBIX Learn

Additional Directories vs Primary Working Directory

People think an added folder works just like the folder Claude Code started in. For files it does: Claude reads and edits both under the same rules. But only the start folder is a home for setup. Its settings, hooks, MCP servers and CLAUDE.md load. An added folder gives file access, and most of its setup stays asleep.

AI⌨️ Claude Code

Additional Directories

More folders Claude may read and edit, beside the first one.

Additional directories are extra folders Claude may read and edit, beside the one you started in. Add them with a flag, a command or a list in settings. They follow the same rules as the main folder. They give file access only. Most of their own settings do not load.

Example
Jack's app uses a shared library in the next folder over. He adds it, and Claude can fix both in one session.
Why it matters
Real work often spans two folders. This opens the second one and no more.
Full entry
AI⌨️ Claude Code

Primary Working Directory

The folder you start Claude Code in, where it reads freely.

The primary working directory is the folder you start Claude Code in. Claude can read files there without asking. Edits follow your permission mode. Project settings, CLAUDE.md and .mcp.json are all found from it. The /cd command moves the session to another one.

Example
Lucy starts Claude Code in her app's folder. It reads every file there without a prompt, but asks before it reads her home folder.
Why it matters
It is the line between free reads and asked reads, and where project settings come from.
Full entry

In one line

Additional Directories
More folders Claude may read and edit, beside the first one.
Primary Working Directory
The folder you start Claude Code in, where it reads freely.