[FEATURE] Add `acceptEditsAndWrites` permission mode

Resolved 💬 2 comments Opened Jan 18, 2026 by maacarbo Closed Jan 19, 2026

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

Currently, the acceptEdits mode only auto-accepts editing existing files, but still prompts for creating new files (Write operations). This distinction seems unnecessary for users who've already opted into auto-accepting edits.

Proposed Solution

Add a new permission mode: acceptEditsAndWrites that automatically accepts both:

  • Edit operations (modifying existing files)
  • Write operations (creating new files)

This would provide a more intuitive workflow for users who want to reduce permission prompts without going to full bypassPermissions mode.

Or make acceptEdits mode include Write operations by default, since the distinction between editing and creating files seems artificial from a user permission perspective.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

User: "Add a new authentication middleware to the Express app"

Current behavior with acceptEdits: true:

  1. Claude edits server.js to import the middleware ✓ (auto-accepted)
  2. Claude creates middleware/auth.js ⚠️ (prompts for permission)
  3. Claude edits routes/users.js to use middleware ✓ (auto-accepted)
  4. Claude creates tests/auth.test.js ⚠️ (prompts for permission)

Result: User gets interrupted twice during a single coherent task, despite having opted into auto-accepting edits.

Additional Context

_No response_

View original on GitHub ↗

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