[FEATURE] Add --acceptEdits flag as cmd line arg just as we can set it via /config in interactive mode

Resolved 💬 3 comments Opened Dec 27, 2025 by iremnuy Closed Dec 27, 2025

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

Hello,

In my project i have several sub-processes started via > claude --print ...... which automates some code tasks. However if i dont set Default permission mode to acceptEdits in the terminal session that the code is being executed, claude keeps asking me for some editing permissions (although all allowed tools do exist in .claude/settings.local.json ) , when i set it via /config to acceptEdits, it stops asking and do the edit to the files. Is there a way to set this arg during cmd line execution so that i would not need to go into the terminal and set the mentioned arg. (Or is it the same thing with --dangerously-skip-permissions ? )

Proposed Solution

I'd like to be able to set the acceptEdits mode as a flag in cmd line like :

claude --print --acceptEdits "Add unit tests to this project"

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

For anyone using claude-cli for a task-automization process, claude halting the process and asking for permission is a huge deal-breaker as usually all the allowed tools (bash or mcp tools or of any kind) are already set in settings.json and they expected to be run without any interrupts, but without setting the mode to acceptEdits via /config those allowed tools in settings.local.json doesnt seem to be executed without asking.

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗