Accept-edits mode is the middle gear. In this mode Claude auto-accepts file edits, so it stops asking permission for every write. But it still pauses before running commands. You get speed on edits and a checkpoint on anything that runs.
What it changes
In default mode, Claude asks before each edit and each command. That is safe, but on a task with many small changes the prompts pile up. Accept-edits mode removes the edit prompts. Claude works through a series of file changes without stopping, then still asks before it runs a command like a test or a git operation.
claude --permission-mode acceptEdits
Or cycle to it with Shift+Tab during a session.
When it fits
Accept-edits shines once you already trust the direction. Good moments include:
- Carrying out a plan you just approved
- A repetitive change across several files
- Fast iteration where you are watching the results closely
The key phrase is watching closely. Auto-accepting edits is comfortable when you can see what is happening and would notice a wrong turn.
Where to be careful
Because edits apply without a prompt, this mode assumes the changes are going the right way. Pair it with a safety net. Work on a branch, keep your changes committed in small steps, and give Claude a check to run so mistakes surface quickly:
npm run lint && npm test
A natural pairing with plan mode
A clean workflow is to plan first, then implement in accept-edits. You use plan mode to agree on the approach with no changes, approve it, and switch to accept-edits so the agreed work flows without constant prompts. Careful up front, fast to carry out.
Comments
Be the first to comment.