[Bug] Plan modifications with ctrl+g are not passed to Claude

Found 1 possible duplicate issue:

1. https://github.com/anthropics/claude-code/issues/9355

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

The found possible duplicate is not a duplicate because my changes are synced back to the claude code, be it when I use it for my prompt or even for this plan — I did see modifications being propagated to the claude code interface after I closed editor, it's just that claude didn't see it changed.

+1

It is still the issue

Editing a plan never worked for me either.

I don't know whether this will be useful to maintainers, but I asked Claude Code to fix this issue inside the minified source code of Claude Code (version 2.0.50). Here is its report:

---

Fix: ExitPlanMode Edited Plans Not Reaching Claude API

Note: Variable names in this document are human-readable approximations. The actual decompiled code uses minified names.

The Bug

When editing a plan via Ctrl+G before approval:

• UI showed edited plan ✓
• User approved ✓
• Claude received original unedited plan ✗

Root Cause

The userModified flag tracking plan edits wasn't properly threaded through the system:

1. UI component tracked edits correctly (state variable set to true on Ctrl+G)
2. UI passed the flag to permission system
3. Permission system ignored it and recalculated based on inputsEquivalent method
4. Plan tools lack inputsEquivalent, so flag defaulted to false
5. Tool received userModified: false even when plan was edited
6. Tool result included plan unconditionally (or not at all)

The Fix

Thread the userModified flag through the entire flow and conditionally include edited plans.

1. UI Component: Pass userModified flag

File: cli.js:~361244

  function approvalHandler(choice) {
      let updatedInput = {
          plan: currentPlan,
+         userModified: wasModified
      };

2. Permission System: Respect UI's flag

File: cli.js:393934

- let userModified = tool.inputsEquivalent ? !tool.inputsEquivalent(originalInput, updatedInput) : false;
+ let userModified = updatedInput.userModified ?? (tool.inputsEquivalent ? !tool.inputsEquivalent(originalInput, updatedInput) : false);
  resolve({
      behavior: "allow",
      updatedInput: updatedInput,
      userModified: userModified
  })

3. Tool: Forward flag to result

File: cli.js:~360983

  return {
      data: {
          plan: planText,
          isAgent: isAgentMode,
+         userModified: context.userModified
      }
  }

4. Tool Result: Conditionally include plan

File: cli.js:360987-361007

- mapToolResultToToolResultBlockParam({isAgent, plan}, toolUseId) {
+ mapToolResultToToolResultBlockParam({isAgent, plan, userModified}, toolUseId) {
      if (isAgent) return {
          type: "tool_result",
-         content: 'User has approved the plan...',
+         content: userModified ? `User has approved the plan...
+
+## Approved Plan:
+${plan}` : 'User has approved the plan...',
          tool_use_id: toolUseId
      };
      return {
          type: "tool_result",
-         content: "User has approved your plan...",
+         content: userModified ? `User has approved your plan...
+
+## Approved Plan:
+${plan}` : "User has approved your plan...",
          tool_use_id: toolUseId
      }
  }

Result

Claude now receives edited plans only when user actually modified them:

• Without Ctrl+G edit: Generic approval message (preserves original API behavior)
• With Ctrl+G edit: Approval message includes edited plan content

<img width="1026" height="265" alt="Image" src="https://github.com/user-attachments/assets/6d70aacd-33b9-4bf6-8b33-43858eedb549" />

No sure about ctrl+g, but I could manage to update the file with the plan (just editing separately ~/.claude/plans/squishy-zooming-starfish.md) and it worked out: Claude Code has executed the update plan without noticing :D

Just another voice to say that ctrl+g to edit the plan does not actually work (using version 2.0.57).

I am also having this issue

+1

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

I tested it now and it seems that it was fixed in the meantime, because it works now. CLosing.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.