Learn one feature at a time

Let Claude edit.
Keep reviewing.

Understand which approvals Accept Edits reduces and why the label differs between local and cloud sessions.

What the label means

Accept Edits reduces prompts for file changes. Locally, acceptEdits also auto-approves mkdir, touch, rm, rmdir, mv, cp, and sed within its permitted scope, including deletions; other actions remain subject to permission rules. In cloud sessions, the label maps differently because file edits are already pre-approved. It does not mean every possible command is approved.

Use it for a change you understand

Select Accept Edits in the interface. In a local terminal:

claude --permission-mode acceptEdits

Implement the README change we just agreed on. Keep the edit to that file. Show the diff and explain the result. Ask separately before committing or publishing anything.

Review the edit itself

1. Open the diff, which shows added and removed lines.
2. Check for unexpected files or unrelated changes.
3. Read any command approval request before accepting it.
4. Run the relevant checks for the approved change.

A mode change is not a quality check. If a change is unclear, ask Claude to explain it or return to Plan. For local review of individual actions, Manual mode is another option. Choose it when the extra interruptions help you understand the work.

Do not confuse these controls

“Accept Edits” is a permission mode. Accepting a proposed plan, applying a diff, and merging a GitHub pull request are separate decisions. Check the control’s label and the scope of the action each time.

References

• Anthropic. (n.d.-f). Choose a permission mode. Retrieved September 24, 2026, from https://code.claude.com/docs/en/permission-modes
• Anthropic. (n.d.-l). Configure permissions. Retrieved September 24, 2026, from https://code.claude.com/docs/en/permissions