[FEATURE] don't ask for any subsequent edit of plan file when I explicitly tell Claude to edit it anytime automatically

Resolved 💬 4 comments Opened Feb 17, 2026 by michaill Closed Mar 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

When a user explicitly grants permission to edit a specific file in the current session (e.g., "you are allowed to do any edit to the plan in this session"), the tool confirmation system should remember that permission and stop prompting for subsequent edits to that same file.

Proposed Solution

Don't enforce this security policy when user explicitly wants to opt out.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

It is frustrating, slowing down the speed and I my capacity is bigger then reading changes line by line. I want to read complex changes (shown in diff), but no matter how I tried it was stucked or asking me for approval of every single edit of the plan file (which is in my home folder and not in project -> this might be the reason). Anyway if I prompt it to allow any other change it was still asking. Then I tried to prompt it to do all the changes in one shot, it showed me in context, but when I told to write all in one, it get stucked.

Additional Context

_No response_

View original on GitHub ↗

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