[FEATURE] Option to COMPLETELY disable "accept edits" on

Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 5 comments · opened Jul 9, 2026 · closed Aug 17, 2026
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

This feature was previously requested here and here but in both cases the issue was closed due to lack of activity. This is still a desired feature, however.

Prior description:

The "accept edits on" feature poses a significant risk in any AI-assisted code editor. In the case of Claude Code, that risk is amplified due to ongoing issues with code quality and frequent hallucinations. For this reason, it's essential to give users the option to completely and unconditionally disable "accept edits on". No automatic code changes should ever occur without explicit user approval. This control is critical to protect the integrity of users' codebases. While the quality and reliability of Claude Code continue to improve, automation must never override user intent. Until the assistant's output is consistently trustworthy, this safeguard is not optional — it's necessary.

Proposed Solution

Prior description:

The "accept edits on" feature poses a significant risk in any AI-assisted code editor. In the case of Claude Code, that risk is amplified due to ongoing issues with code quality and frequent hallucinations. For this reason, it's essential to give users the option to completely and unconditionally disable "accept edits on". No automatic code changes should ever occur without explicit user approval. This control is critical to protect the integrity of users' codebases. While the quality and reliability of Claude Code continue to improve, automation must never override user intent. Until the assistant's output is consistently trustworthy, this safeguard is not optional — it's necessary.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

While this technically has potential duplicates, as far as I can tell all of them have been closed by bots. I'll be sure to set a reminder to keep this one open.

View original on GitHub ↗

4 Comments

matt-lachman-trss · 2 months ago

Keep alive.

bcherny collaborator · 1 month ago

You can enforce this today with ask rules, which force a prompt in every permission mode (including accept-edits, auto, and even bypass). Add to your settings:

{
  "permissions": {
    "ask": ["Edit", "Write", "NotebookEdit"]
  }
}

Every file change then requires your explicit approval regardless of which mode is active. Put it in managed settings to enforce it org-wide.

Docs: https://code.claude.com/docs/en/permission-modes and https://code.claude.com/docs/en/permissions

🤖 Generated with Claude Code

matt-lachman-trss · 1 month ago

@bcherny I have had varying degrees of success with that, but honestly, what you're talking about is a workaround, not a feature.

For long-running sessions, I have noticed Claude begins to ignore rules / assume approval quite a bit. For that reason, the workaround you have suggested is insufficient.

I want to be able to TRULY disable auto-mode so that it is impossible to accidentally slip into it, and impossible for Claude to bypass rules.

Please reopen this ticket.

matt-lachman-trss · 1 month ago

In the absence of further commentary, I have opened a new ticket and referenced this one. https://github.com/anthropics/claude-code/issues/87973

Showing cached comments. Read the full discussion on GitHub ↗