[BUG] Session permission mode 'acceptEdits' not persisting - repeated Edit permission prompts on Linux

Same here for macOS as well. It's so annoying und makes the permission system completely useless.
For every batch command, which is allowed in the .claude/settings.local.json, Claude Code asks EVERY time, when it wants to execute it.

How on earth can this not be fixed for three weeks?! This makes Claude UNUSABLE!!

Running into this a lot today too.

@bcherny Is this in development? It seems like the old issue is was automatically closed due to inactivity (https://github.com/anthropics/claude-code/issues/11206)

Same problem on Windows. Makes Claude Code CLI almost usable. I have to babysit every single edit on text files for example

I love how the bot closes the new duplicates then closes the original issue due to no activity

Still experiencing this issue on Arch Linux with Claude Code 2.1.5.

Environment

• Platform: Arch Linux (kernel 6.18.3-zen1-1-zen)
• Claude Code version: 2.1.5
• Installation: Native CLI

Reproduction

Same as OP - selecting "Yes, and apply to all edits in this chat" does not persist. Every subsequent Edit operation prompts again.

Workaround

Adding explicit Edit(**/*) to .claude/settings.local.json bypasses the issue:

{
  "permissions": {
    "allow": [
      "Edit(**/*)"
    ]
  }
}

This confirms the bug is in the session mode check, not the permission system itself.

Still experiencing this issue.

Environment

• Platform: macOS (Darwin 25.1.0)
• Claude Code version: 2.1.6
• Installation: Native CLI

Same behavior as described - selecting "Yes, allow all edits during this session" does not persist. The very next edit to the same file still prompts for permission.

Same on 2.1.7/macos arm64/brew install.

Only way to get around it is bypass permissions mode. Cycling permissions mode back to accept edits doesn't fix it either.

Worth noting that I always run claude with this flag, and my default mode is acceptEdits, but I have seen it _sometimes_ follow the accept edits permissions setting.

this has been happening for weeks now on my machines - both windows and linux. i've been so hoping it would have been fixed by now. relying on --dangerously-skip-permissions is not a good solution as its a bit aggressive.

happening using native CLI on both linux (arch linux) and windows 11. please fix! there is nothing better than having it ask me to accept edits 20 times for the same file in under 2 minutes.

Confirming this also occurs on Windows (not just Linux/WSL). Filed #21835 as duplicate before finding this issue.

Environment: Windows 11, Claude Code 1.0.29 (Opus 4)

Same behavior: selecting "Yes, and don't ask again for this session" for Edit/Bash operations does not persist - permission prompts reappear on subsequent tool calls within the same session.

+1 for a fix. This creates significant friction in longer sessions.

+1 — also reproduces in the VS Code extension, not just the CLI. Same root symptom (mode silently reverts to "Ask before edits"), but the trigger here is Developer: Reload Window / VS Code restart rather than mid-session.

• VS Code: 1.115.0 (41dd792b5e652393e7787322889ed5fdc58bd75b, x64)
• Claude Code extension: 2.1.101
• Claude CLI: 2.1.104
• OS: Debian 13 inside a Dev Container on WSL2 (Windows host)

All four settings layers (.vscode/settings.json initialPermissionMode + allowDangerouslySkipPermissions, project .claude/settings.json, global ~/.claude/settings.json) declare bypassPermissions and are all ignored on reload. Reproducible for ~1 week on this setup.

If the root cause analysis in the OP holds (session mode being set but not consulted), it'd be worth checking whether the VS Code extension's startup path has the same "set, never check" flaw when reading initialPermissionMode.