[BUG] Claude continually asks for permission, even after selecting yes, always allow.

[Jkrise]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

When asking Claude to do anything, it asks for permission first. If I select yes, always allow, the next time it does the same thing, it asks again, over and over. I've tried local and global permissions, but it keeps doing the same thing.

What Should Happen?

Claude should remember the user's choices

Error Messages/Logs

Read file

  Read(AP-Cleanup-Documentation.md)

 Do you want to proceed?
 ❯ 1. Yes
   2. Yes, during this session
   3. No, and tell Claude what to do differently (esc)

Steps to Reproduce

Ask Claude the scan the directory
Wait for the prompt for permission
select yes, always allow
Repeat the request to scan the directory again and it will ask for permission again

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.0.36 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Asking permission too often #10629
2. [Bug] "Always allow" settings not persisting to .claude/settings.local.json #11172
3. [BUG] Claude Code will not do anything without manual authorisation every single step #7161

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

[nspady]

I am having the same issue. It seems to occur when a general subagent is spun up and attempts to take action. If a specific subagent is used the permissions set for that agent apply as expected.

[andrewSaros]

I am having the same issue when I was using a network resource \\10.0.0.10\files\claude, this was working for well over a month and I was working on it yesterday. Setting permissions and any other fixes that claude suggested didn't have any effect. In the end I mapped the network drive and this seems to fix the issue.

[michaelchrisco-stack]

Yeah, doesn't matter if you have this in your global, project, vscode, settings. Note it told me that Bash used a different format, but still doesn't work. Hmm it changes the format here but anyway

"permissions": {
"allow": [
"Read()",
"Write()",
"Edit()",
"Glob()",
"Grep(**)",
"Bash(::)"
],

It won't stop asking unless this is in this file. Not ideal but if you are tired of it. You then have the ability to shift tab thru 3 options. Plan, Accept, Bypass and only bypass works so if after you get, they plan together you can switch and not have to say yes, all the time and hope it behaves as you watch it.

C:\Users\YourUser.claude\settings.json
"defaultMode": "bypassPermissions",

[cruftyoldsysadmin]

This has been a problem since day one. This is the single largest flaw in Claude Code, and it should really be Anthropic's highest priority. Even YOLO mode prompts for endless permissions.

[patrickkidd]

I also see this issue, where at least the user's global permissions are ignored. It doesn't seem to matter what rule. I have auto-updates enabled, using macOS sequoia.

[cmwalton]

I'm experiencing this same issue on version 2.0.50, so it's still present in the latest release. This was working correctly before version 0.36 but has been broken since then.

This is incredibly frustrating, especially when working with long files. I'll often ask Claude Code to read a file, switch to a different task, and come back only to find it's been sitting there waiting for permission to read part of the file - permission I already granted! The whole point of "always allow" is to avoid this exact scenario.

The workflow disruption is significant, particularly when dealing with large files that need to be processed in sections. Having to babysit permission prompts defeats the purpose of having an AI assistant handle these tasks autonomously.

[kas-kad]

I would suggest checking settings.local.json. I had my project's permissions configured thoroughly in settings.json file which had no effect until I duplicated it and renamed to settings.local.json. After that everything went smoothly.

according to docs settings.local.json is "non-checked" settings, personal prefs, whereas settings.json are "checked" settings can be shared across team. But it's not very clear how should they co-exist, seems like in my case settings.json was partially ignored

[SimonDedman]

Experiencing the same issue; detailed comment on #11172 with additional evidence that even manually-added glob patterns in settings.local.json are not being respected
(v2.0.59, Linux)