claude-code - 💡(How to fix) Fix [Bug] Relative path permissions glob pattern (.*) applies incorrectly to subdirectories [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55528Fetched 2026-05-03 04:51:03
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×2

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description ~/.claude/settings.json の仕様について、permissionsオプション内のRead、Edit、Write の挙動で、(./)を設定すると、ホームディレクトリ配下が適用範囲になる。絶対パスでは問題ないことは確認した。推測するに、配下ディレクトリに(./)の文字列で適用してしまっているのではないかという疑惑。

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.126
  • Feedback ID: 4e01c31f-989d-48a0-8859-53f51a17da9e

Errors

[]

extent analysis

TL;DR

The issue may be resolved by using absolute paths instead of relative paths with wildcards in the permissions option of the ~/.claude/settings.json file.

Guidance

  • Verify that the issue is indeed caused by the use of relative paths with wildcards by testing with absolute paths.
  • Check the documentation for the ~/.claude/settings.json file to see if there are any specific guidelines for using wildcards in the permissions option.
  • Consider escaping or quoting the wildcard character to prevent it from being interpreted as a directory specifier.
  • Test the behavior with different types of paths (e.g., /path/to/dir/*, ./dir/*, ~/dir/*) to see if the issue is specific to certain types of paths.

Notes

The issue seems to be related to the interpretation of wildcards in the permissions option, but without more information about the expected behavior, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: use absolute paths instead of relative paths with wildcards, as this has been confirmed to work in the issue description.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Bug] Relative path permissions glob pattern (.*) applies incorrectly to subdirectories [2 comments, 2 participants]