claude-code icon indicating copy to clipboard operation
claude-code copied to clipboard

[BUG] "Allow all edits" setting not respected during session

Open jkaster opened this issue 2 months ago • 42 comments

Preflight Checklist

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

What's Wrong?

Bug Report: "Allow all edits" setting not respected during session

Description

When I select "Allow all edits" at the start of a Claude Code session, the tool continues to prompt me for approval on every individual file edit throughout the session. This makes batch editing workflows extremely tedious.

Impact

  • Severity: High for users doing refactoring or batch updates
  • Workflow disruption: Makes multi-file operations impractical
  • User friction: Requires constant manual intervention for routine tasks

Environment

  • Claude Code version: Latest (October 2025)
  • OS: macOS (Darwin 24.6.0)
  • Node version: >=24.6.0

Workaround

None - users must manually approve each edit

Suggested Fix

  • Persist "Allow all edits" setting for entire session duration
  • Or provide session-level edit approval settings in configuration
  • Or add a command-line flag for unattended edit mode

Related Context

This occurred while fixing agent-to-agent communication issues across 9 markdown configuration files in .claude/commands/flow/ directory.

What Should Happen?

Expected Behavior

After selecting "Allow all edits", all Edit tool operations within the session should proceed without additional approval prompts.

Actual Behavior

Despite selecting "Allow all edits", I continued to be prompted:

  • "You need to do that with a lot more agents than just rebuild.md. Can you go ahead and perform all edits/fixes without prompting me each time?"
  • "I keep answering 'allow all edits' and you keep prompting me for every edit and it's very tedious."

Error Messages/Logs


Steps to Reproduce

Steps to Reproduce

  1. Start Claude Code session
  2. Request multiple file edits (e.g., "fix these 9 agent files")
  3. Select "Allow all edits" when first prompted
  4. Observe that subsequent Edit tool calls still require individual approval

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.14 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

jkaster avatar Oct 11 '25 04:10 jkaster

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/9147
  2. https://github.com/anthropics/claude-code/issues/9326
  3. https://github.com/anthropics/claude-code/issues/8215

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

github-actions[bot] avatar Oct 11 '25 04:10 github-actions[bot]

This is marked as a duplicate of a bug that says it was fixed in a different release but I'm on the latest version of Claude Code for the Mac as indicated in my ticket, and the issue still exists.

⏺ You're running Claude Code version 2.0.14.

Since the GitHub releases page doesn't show version information, you can check for updates by running:

npm update -g @anthropic-ai/claude-code

Or to see if there's a newer version available without updating:

npm outdated -g @anthropic-ai/claude-code

Would you like me to check for updates?

yes

⏺ Bash(npm outdated -g @anthropic-ai/claude-code) ⎿  (No content)

⏺ Good news! You're already on the latest version. The command returned no output, which means version 2.0.14 is the current latest version of Claude Code.

jkaster avatar Oct 11 '25 05:10 jkaster

My Claude code version is also 2.0.14 and also has the issue of not allowing all edits

driekey avatar Oct 11 '25 08:10 driekey

Same issue. I have to approve every edit manually. But it seems like it's only affecting files in .claude directory.

balabis avatar Oct 12 '25 07:10 balabis

I'm also experiencing this, specifically for agent files in my .claude/agents folder. I'm running v2.0.14

petehamilton avatar Oct 14 '25 07:10 petehamilton

sadly, bug still exists in v2.0.15

jkaster avatar Oct 14 '25 21:10 jkaster

I'm experiencing this outside of the .claude folder. It's unclear to me which folders are or are not affected; sometimes it happens, sometimes it doesn't

amosjyng avatar Oct 16 '25 07:10 amosjyng

Still exists in v2.0.17 also

jkaster avatar Oct 16 '25 16:10 jkaster

Just FYI, I am having this issue on Ubuntu. v2.0.15

iconjack avatar Oct 19 '25 03:10 iconjack

Still exists in v2.0.24 (running on MacOS)

apman avatar Oct 21 '25 02:10 apman

Same on v2.0.27 on Win 11 / WSL 2 Ubuntu. I feel like I notice it more when I'm running claude more than once, in different repos. Though I may notice it more because I'm just running more instances and it's not related. I wish I had a way to fix or restore the setting. It seems to be related to the conversation as exiting claude starting again claude -c, Selecting 2. Yes, allow all edits during this session (shift+tab) doesn't work. The bug sticks with the conversation.

pinkwerks avatar Oct 26 '25 17:10 pinkwerks

This bug still exists in v2.0.28 (on Mac)

This has become insanely annoying and extremely unproductive. I need to explicitly approve every tiny change to every file in my work repository's .claude/skills (or other) folder because "allow edits" is completely ignored. How can I increase the priority of this fundamental UX issue?

Why has it been dropped from oncall? Do you have any plan to fix it?

jkaster avatar Oct 29 '25 17:10 jkaster

@jkaster, I got it to make this note in the .Claude file - that seems to have solved the problem, except it's not session-based now:

**IMPORTANT**: You have blanket permission to edit ALL files in this repository (bla/bla/**). This permission is configured in .claude/settings.local.json` and you should NEVER ask for permission to edit files in this directory. Just make the edits directly using the Edit or Write tools.

apman avatar Oct 30 '25 00:10 apman

Huh! I think I tried to scope that to the .claude folder and it didn't take. Thanks for the suggestion, I'll try variations on this theme and see what happens!

jkaster avatar Oct 30 '25 03:10 jkaster

as a reasonable but tedious workaround I've been telling it to use python or ts to write file processing scripts that generate patch files to update all files that need a change in a batch, when doing refactors via prompt

jkaster avatar Oct 30 '25 03:10 jkaster

tried your suggestion. sadly it didn't work for the .claude/** folders, which is the only way I would be willing to turn it on. So this bug is still biting me for every single tiny edit Claude Code does.

On Wed, Oct 29, 2025 at 5:38 PM Anna Malchow-Perryman < @.***> wrote:

apman left a comment (anthropics/claude-code#9348) https://github.com/anthropics/claude-code/issues/9348#issuecomment-3465596802

@jkaster https://github.com/jkaster, I got it to make this note in the .Claude file - that seems to have solved the problem, except it's not session based now:

IMPORTANT: You have blanket permission to edit ALL files in this repository (bla/bla/**). This permission is configured in .claude/settings.local.json` and you should NEVER ask for permission to edit files in this directory. Just make the edits directly using the Edit or Write tools.

— Reply to this email directly, view it on GitHub https://github.com/anthropics/claude-code/issues/9348#issuecomment-3465596802, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABORGAQMMG7L6Q2LMV6AGGT32FMXVAVCNFSM6AAAAACI4UPEYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINRVGU4TMOBQGI . You are receiving this because you were mentioned.Message ID: @.***>

jkaster avatar Oct 30 '25 03:10 jkaster

i'm on 2.0.32 and can confirm the bug is still there

colintoh avatar Nov 04 '25 03:11 colintoh

Same here when editing claude skills at .claude/skills/ it doesn't respect the accept edits on

jhagege avatar Nov 06 '25 13:11 jhagege

Same here. It's not really an agent when you have to accept edits every time. Disappointing this has not been fixed.

ma225tq avatar Nov 07 '25 09:11 ma225tq

This started for me a couple of days ago. The odd thing is that it's only specific files that it asks for permission on, and the files it asks before editing are always files that were created during the session. Other files it edits just fine without asking for permission.

solsystemlabs avatar Nov 08 '25 19:11 solsystemlabs

This happens to me too on v2.0.36.

same

The odd thing is that it's only specific files that it asks for permission on, and the files it asks before editing are always files that were created during the session. Other files it edits just fine without asking for permission.

It seems it occurs when filenames include $

Eiji-Kudo avatar Nov 09 '25 14:11 Eiji-Kudo

Same for 2.0.37

garvae avatar Nov 13 '25 11:11 garvae

Kinda crazy ... this creates such friction I've actually had a much better experience using cursor-agent to develop the skills rather than Claude Code. You'd think Anthropic would care about this. 🤷🏼

jkaster avatar Nov 13 '25 18:11 jkaster

Observing it on v2.0.42 while building a skill in .claude/skills, it's extremely frustrating.

FabianFrank avatar Nov 15 '25 03:11 FabianFrank

+1 - much more difficult to use with this bug

snlamm avatar Nov 16 '25 10:11 snlamm

This started happening to me since v2.0.42 whereas previously it was working as intended (v2.0.36 or so). Windows 11 through cursor

AndyLearnsAI avatar Nov 16 '25 13:11 AndyLearnsAI

Same thing started to happen to me on v2.0.42 (linux) for any file that is getting edited, it started yesterday for me.

Note: It seems that rolling back to v2.0.37 solves the issue.

deviantony avatar Nov 17 '25 06:11 deviantony

This problem has persisted for me for at least 4 months, even in YOLO mode. Permissions in Claude CLI are inherently broken. When I use openai, it actually respects permissions (and agents, and skill uses).

cruftyoldsysadmin avatar Nov 17 '25 08:11 cruftyoldsysadmin

On macOS, I fixed this by removing the npm-based installation and re-installing via the standalone install command:

npm uninstall -g "@anthropic-ai/claude-code"
curl -fsSL https://claude.ai/install.sh | bash

victorlin avatar Nov 21 '25 20:11 victorlin

On macOS, I fixed this by removing the npm-based installation and re-installing via the standalone install command:

npm uninstall -g "@anthropic-ai/claude-code" curl -fsSL https://claude.ai/install.sh | bash

Tried this in Win 11 (irm instead of curl) and it didn't work :( Still asking me to approve edits.

AndyLearnsAI avatar Nov 21 '25 23:11 AndyLearnsAI