[Feature Request] Add option to skip trust prompt when .claude/settings.local.json allows it
Bug Description
Feature request: Option to skip trust prompt when settings.local.json exists
Use case: I use git worktrees extensively, with a shared settings.local.json symlinked across all worktrees. Each
worktree is a different absolute path, so I get the "Do you trust the files in this folder?" prompt every time I open
Claude in a new worktree - even though I've already explicitly configured my permissions in settings.local.json.
The problem: The existence of a .claude/settings.local.json file with permissions.allow entries is itself an explicit
declaration of trust. Prompting me to confirm trust for a directory where I've already placed a carefully crafted
settings file is redundant. I wrote the file - I obviously trust it.
Proposed solution: Add a setting (in ~/.claude/settings.json or CLI flag) like:
{
"trustProjectsWithLocalSettings": true
}
Or a CLI flag: --trust-local-settings
When enabled, if .claude/settings.local.json exists in the project, skip the trust prompt entirely. The settings file IS
the trust declaration.
Current workaround: Manually accepting the prompt in every new worktree, which defeats the purpose of having shared,
pre-configured settings.
Environment Info
- Platform: linux
- Terminal: gnome-terminal
- Version: 2.0.57
- Feedback ID: 78151e3f-2e79-41b7-91b9-a7d8f95748c0
This issue has 13 comments on GitHub. Read the full discussion on GitHub ↗