Support whitelisting trusted directories independent of where Claude is started

[mikehearn]

I'm using the worktree tip (thanks Boris!) and I'd like to whitelist the directory where all the worktrees are placed even though they're independent projects. I don't see a way to do this, so in every new worktree Claude always asks me afresh. It'd be nice to be able to say I trust everything underneath a folder without it becoming a 'project'.

[coygeek]

Hey

I was digging through the official docs and think I found a solution for your git worktree workflow. It seems like you can solve this by using the user-level settings file, which applies globally to all your Claude Code sessions.

You can add rules to ~/.claude/settings.json to pre-approve directories and common commands. This should stop Claude from asking for permission in every new worktree.

Based on the documentation, you can use two key settings:

1. additionalDirectories: This lets you grant Claude access to directories outside of the one it was started in. You can add your main worktree parent folder here.
2. permissions.allow: This lets you whitelist specific tools or commands (like npm test or git diff) so you don't have to approve them every time.

Here’s an example of what you could put in your ~/.claude/settings.json file:

{
  "permissions": {
    "additionalDirectories": [
      "~/path/to/your/worktrees-parent-folder"
    ],
    "allow": [
      "Bash(npm run test:*)",
      "Bash(npm install)",
      "Bash(git diff:*)",
      "Read(~/.gitconfig)"
    ]
  }
}

Just replace ~/path/to/your/worktrees-parent-folder with the actual path to the directory containing all your worktrees. With this setup, any new worktree you create under that parent folder should inherit these settings automatically.

This is covered in the "Identity and Access Management" and "Claude Code settings" sections of the documentation if you want to read more.

Hope this helps streamline your process

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[github-actions]

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.