Documentation update for security. Claude overrides rules but this is not obvious and only reveals it after pain. Update documentation giving abstraction solution PLEASE

Status Closed — not planned

Maintainer reply None cached

Activity 9 comments · opened Oct 19, 2025 · closed Jan 8, 2026

Bug Report: Wildcard Permissions Not Working

Version: 2.0.22 (Claude Code)
Platform: Windows (PowerShell)
Severity: CRITICAL - Makes Claude Code unusable for basic operations
Time Lost: 3+ hours of session restarts

---

Summary

Claude Code ignores Bash(*) wildcard permission in .claude/settings.local.json and prompts user for approval on EVERY Bash command, including basic commands like dir.

---

Configuration

File: .claude/settings.local.json

{
  "permissions": {
    "allow": [
      "Read(*)",
      "Edit(*)",
      "Write(*)",
      "Bash(*)"
    ],
    "deny": [],
    "ask": []
  },
  "dangerously-skip-permissions": true
}

Status: File exists and is loaded by Claude Code.

---

Expected Behavior

With "allow": ["Bash(*)"] AND "dangerously-skip-permissions": true:

ALL Bash commands should execute WITHOUT user prompts
No exceptions

---

Actual Behavior

Claude Code prompts user for approval on EVERY Bash command, including:

dir .claude

When user rejects the prompt (because it's absurd to need permission for dir):

The user doesn't want to proceed with this tool use. The tool use was rejected

Result: Session becomes unusable, requiring complete restart.

---

Impact

CRITICAL - Makes Claude Code completely unusable:

User has had to restart sessions repeatedly for 3 hours
Cannot run basic directory listings
Cannot run npm, git, or any build commands without manual approval
Every rejection breaks the session
No workaround available

User quote: "i have had to restart your session over and over for 3 hours"

---

Reproduction Steps

Create .claude/settings.local.json with:

``json { "permissions": { "allow": ["Bash(*)"] }, "dangerously-skip-permissions": true }``

Have Claude attempt to run ANY Bash command (e.g., dir, ls, npm install)

OBSERVE: User is prompted for approval despite wildcard permission and skip-permissions flag

---

Questions

Is Bash(*) wildcard matching actually implemented?
Does dangerously-skip-permissions: true actually work?
Is there a difference between .claude/settings.json vs .claude/settings.local.json?
Are there any hidden config files that override these settings?
Is there a debug mode to see which permissions are actually loaded?

---

Environment

Claude Code Version: 2.0.22
Platform: Windows
Shell: PowerShell
GitHub CLI: v2.81.0

---

Recommended Fix

The permissions system needs to:

Actually respect Bash(*) wildcard permissions
Actually respect dangerously-skip-permissions: true
Stop prompting when both are set

This is blocking basic usage of Claude Code for Windows users.

View original on GitHub ↗

9 Comments

github-actions[bot] · 12 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Badajoz95 · 12 months ago

I just lost 3-4 hours work with Claude in VS code giving me every reason under the sun as to what was the reason. It gave me random answers but was not able to clearly specify what its own config should be. I used just * and could not do dir. I tried dangerous and nothing happened. To critique the documentation by Claude on how to configure this so bad that your own AI can't fix it. Either this is a really bad bug, by design or something. I can't click EVERY prompt. Provide simple examples to by pass in DEV please. Please provide clear instructions or fix what is a horrid bug

Badajoz95 · 12 months ago

OK enough rage from me.... reminded me of debugging... I think you should close this because it is by design... The engine will ignore any setting that it thinks is too permissive though you can argue with it. Fair play. Now that I know I have to get it to dog food abstraction all my problems went away. Please make that obvious to the AI and it should explain and give a cool, secure abstraction / facade pattern or such like which is simple once you realise lolz.

OptimusPi · 11 months ago

I told Claude Code this is so annoying that I spun up an Auto Clicker program to press the yes button. Claude told me that is a very genius workaround, to use an auto clicker. 💀 (p.s. don't actually do this)

OptimusPi · 11 months ago

p.s. even for a research task, where Claude cloned a git repo, and wants to look at the local files in/tmp/, it keeps asking over and over if it can simply read the files it just cloned :(

Example:
<img width="1020" height="366" alt="Image" src="https://github.com/user-attachments/assets/31f4e342-0da6-43ca-a6ed-9a9bb564d0c6" />

Not sure why it needs permission to cat a file, or why it's trying cat in the first place..

github-actions[bot] · 10 months ago

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.

OptimusPi · 10 months ago

still happens, even in the damn git worktrees in Claude Desktop's Claude Code it does this :)

github-actions[bot] · 9 months ago

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.