[FEATURE] Trusted workspace patterns to skip trust prompt for git worktrees

[chasemcdo]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Note: This was previously reported in #993 and #21283, both auto-closed without resolution. A comment on #993 suggested additionalDirectories as a workaround — I've tested this and confirmed it does not skip the workspace trust prompt (tested with absolute paths, ~ expansion, and wildcard patterns).

Problem Statement

When using git worktrees, every new worktree creates a new directory that Claude Code has never seen before. This triggers the workspace trust prompt ("Quick safety check: Is this a project you created or one you trust?") every single time.

For developers who use worktrees heavily (one worktree per feature branch), this becomes repetitive friction. The parent repository is already trusted, and all worktrees are derived from it — there's no security benefit in re-prompting for each one.

Proposed Solution

Add a trustedWorkspacePatterns (or similar) setting in ~/.claude/settings.json that accepts glob patterns for directories that should be automatically trusted:

{
  "trustedWorkspacePatterns": [
    "~/worktrees/my-project/*",
    "~/repos/**"
  ]
}

When Claude Code launches in a directory matching any of these patterns, the trust prompt would be skipped.

Alternative Solutions

• additionalDirectories: Tested all of the following in global ~/.claude/settings.json — none skip the trust prompt:

  • Absolute path: /Users/me/worktrees/my-project
  • Tilde path: ~/worktrees/my-project
  • Absolute with wildcard: /Users/me/worktrees/my-project/*
  • Tilde with wildcard: ~/worktrees/my-project/*

  This setting only controls file access scope from within an already-trusted session — it does not affect the initial workspace trust prompt.

• --dangerously-skip-permissions: Disables all permission checks, not just the trust prompt. Overkill for this use case.

• -p flag: Skips trust but only works in non-interactive mode.

• Manually confirming each time: Current workaround, but adds unnecessary friction on every new worktree.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

1. Developer works on a monorepo at ~/repos/my-project/
2. They create worktrees via git worktree add ~/worktrees/my-project/feature-xyz feature-xyz
3. They run claude in the new worktree directory
4. Currently: trust prompt appears every time for each new worktree
5. With this feature: directories under ~/worktrees/my-project/* would be auto-trusted via a glob pattern

Additional Context

• Support whitelisting trusted directories independent of where Claude is started #993 — Original request for this feature, auto-closed after 60 days of inactivity
• Workspace trust prompt appears repeatedly - settings not persisting #21283 — Related report about trust prompt not persisting, closed as duplicate
• The additionalDirectories suggestion from Support whitelisting trusted directories independent of where Claude is started #993 has been independently verified as not solving this problem across multiple path formats

[michaellarocca90]

Upvoting, this would be a great feature.

[aroman]

though minor, this is a very real point of friction for any serious worktree-heavy workflows. big +1!

[mnott]

Workaround: Parent directory trust cascading

The trust state is stored in ~/.claude.json under the projects key per directory path. Crucially, Claude Code walks parent directories when checking trust — so if a parent is trusted, all subdirectories inherit that trust.

One-liner fix — add your home directory (or any common root) as trusted:

python3 -c "
import json
with open('$HOME/.claude.json', 'r+') as f:
    d = json.load(f)
    d.setdefault('projects', {}).setdefault('$HOME', {})['hasTrustDialogAccepted'] = True
    f.seek(0); json.dump(d, f, indent=2); f.truncate()
"

This works for the home directory bug (#18942), git worktrees, and any new directory you open — no prompt ever again.

Found by reverse-engineering the compiled binary: the check function (checkHasTrustDialogAccepted) iterates up the directory tree via while(!0) { if(T.projects?.[_]?.hasTrustDialogAccepted) return true; ... }.

That said, a proper trustedWorkspacePatterns setting as proposed in this issue would be the clean solution — the workaround above is a blunt "trust everything" approach.

[apaz-cli]

Upvote, as this would make it possible to do bash -c 'claude --new-flag /usage'. Or rather it would be cool if it was exposed such.

[mvanhorn]

+1 — I frequently launch Claude Code from my home directory and get this prompt every single session, even with bypassPermissions already set in settings.json. A trustedDirectories setting (or respecting the existing permission mode as implicit trust) would be a great quality-of-life improvement.

[JungHoonGhae]

+1 on this. My use case is slightly different from worktrees but the core problem is the same.

I run Claude Code from my home directory (~) because I frequently need to edit dotfiles and system-level config files. Every single session, I get the trust prompt, and selecting "Yes, I trust this folder" does not persist — it asks again on the next launch.

Environment:

• macOS (Darwin 25.2.0, Apple Silicon)
• Claude Code v2.1.76
• Shell: fish
• ~/.claude/settings.json has bypassPermissions mode enabled

Observed behavior:

• No trust-related key is written to ~/.claude.json after confirming trust
• No trustedDirectories file is created anywhere under ~/.claude/
• The prompt reappears on every new session in the same directory

A trustedWorkspacePatterns setting (or even a simple trustedDirectories list) would solve this for both worktree users and home-directory users alike.