[BUG] Claude Code will not do anything without manual authorisation every single step

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/7148
2. https://github.com/anthropics/claude-code/issues/7145
3. https://github.com/anthropics/claude-code/issues/5140

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

Thanks for reporting this bug, we're working on a fix. In the meantime, if you need to work around this issue, you can temporarily downgrade to v1.0.102 where this functionality is working correctly.

Im having the same issues man its super frustrating

I can't seem to downgrade without it immediately upgrading itself again, even with auto-updates (supposedly) disabled.

@bogini I really hope release quality will improve again. The recent changes - from working permissions in 1.0.102, to file reading issues in 1.0.103, then fixing those but now ignoring general permissions in 1.0.105 - feel rushed, especially without an updated changelog. Many enterprise developers already rely on Claude Code in their workflows, and basic issues like these can suddenly block development entirely. Downgrading only provides a temporary fix since Claude keeps updating. Disabling auto-updates is a workaround, but it obviously raises the question of when it’s safe to update again.

I agree that release quality must be better, QA is failing hard

@bogini I really hope release quality will improve again. The recent changes - from working permissions in 1.0.102, to file reading issues in 1.0.103, then fixing those but now ignoring general permissions in 1.0.105 - feel rushed, especially without an updated changelog. Many enterprise developers already rely on Claude Code in their workflows, and basic issues like these can suddenly block development entirely. Downgrading only provides a temporary fix since Claude keeps updating. Disabling auto-updates is a workaround, but it obviously raises the question of when it’s safe to update again.

Thanks for the feedback, will share with the team.

A new version 1.0.106 was just released that should fix the underlying bug (changelog), please let me know if you continue having any issues. Thanks!

Hii i am at claude code version 1.0.107 and i am literally fratrated cuz of this permission ask again and again even to read a file in same project

<img width="361" height="73" alt="Image" src="https://github.com/user-attachments/assets/af189f99-a024-4a1b-aa18-1f33e884793c" />

<img width="2044" height="242" alt="Image" src="https://github.com/user-attachments/assets/e5fc2050-0e67-454b-b691-635d82cb7dcd" />

see this my .claude/settings.local.json full of mutliple permission list asking again and again

<img width="1034" height="1563" alt="Image" src="https://github.com/user-attachments/assets/9153f8f8-3397-4f6d-98dd-5f9344e64179" />

@bogini please
Help us to fix this issue or release new patch for this literally its asking me permission for each steps again and agin for same files

@Ariz-z This is very concerning! Are you seeing Claude Code add duplicate rules to your settings.local.json? Can you also confirm the format of the automatically added Read rules? As of 1.0.106, these should be in POSIX format and look like Read(//F/GameEssentials/...) but your screenshot seems to show the old format.

@bogini here is my settings.local.json

settings.local.json

ACK thanks, will share with the team to investigate

@bogini is their any update? i cant do work on my projects cuz of this issue

After updating to 1.0.107 (and now 1.0.108) it works mostly fine again. But I feel permissions are maybe not completely respected. I don’t have proof and I didn’t find a pattern, so I am not sure if this is really still an issue, but it feels off somehow.

For example, the permission Bash(find:*) is in my settings.json, but sometimes it still asks for permission to run commands like:

find resources/js -name "*.tsx" -o -name "*.ts" | xargs grep -n "dataSource" 2>/dev/null

And interestingly it only gives the option to run it or tell Claude what to do differently. The third option to remember it for the future is not there in this case. Auto-accept is on.

Again, not sure if it’s really an issue because mostly it works, but it feels off.

Confirmed with other commands too: The settings.local.json has Bash(mkdir:*) maintained and still, Claude asks for permissions to execute mkdir -p "docs/$(date +%Y%m%d) not giving the "middle" option to always accept this action and therefore update the settings.

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.

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.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.