[BUG] Plan mode: after "No, keep planning" feedback, the revised plan is never re-shown and edits start without a second approval #87587

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report
• I am using the latest version of Claude Code

What's Wrong?

When Claude finishes a plan in plan mode, the approval card offers three choices:

1. Yes, and auto-accept edits
2. Yes, and manually approve edits
3. No, keep planning

If I pick option 3 and then type feedback ("also handle X", "change step 2 to Y"), Claude does incorporate the feedback and produces a revised plan — but the revised plan is never shown to me again. There is no new approval card, no re-rendered plan, and no diff of what changed. Claude simply continues and, on the same or the very next turn, starts making file edits.

So the feedback path effectively becomes an implicit approval: I asked to keep planning, and instead I got execution of a plan I was never allowed to read.

Two concrete consequences:

• I cannot verify that my feedback was understood correctly before code is written.
• The second approval gate is skipped entirely, so option 3 is strictly more dangerous than option 2 — asking for more review gets me less.

What Should Happen?

After giving feedback via "No, keep planning", Claude should re-present the updated plan through a fresh ExitPlanMode approval card showing the full revised plan (ideally highlighting what changed), and wait for a new explicit approval before any Edit/Write/Bash mutation runs.

At minimum, no file mutation should happen after a "keep planning" response until a new approval card has been shown and accepted.

Steps to Reproduce

1. Start Claude Code and enter plan mode (Shift+Tab until "plan mode on", or /plan).
2. Ask for something multi-step, e.g. add a dark mode toggle to the settings page and persist the choice in localStorage.
3. Wait for Claude to present the plan and the three approval options.
4. Choose option 3, No, keep planning.
5. Type a change request, e.g. also persist it per-user in the database, not just localStorage.
6. Observe: Claude acknowledges the feedback and revises the plan internally, but no updated plan is rendered and no new approval card appears — it proceeds to edit files.

Expected at step 6: a new plan approval card containing the revised plan.

Claude Model

Opus

Is this a regression?

I don't know

Claude Code Version

2.1.234 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other (Ghostty)

Additional Information

Related but distinct existing issues (none cover this exact path):

• Plan mode needs a discuss/debate state that doesn't wipe the plan view #86467 — asks for a discuss/debate state that doesn't wipe the plan view (about freeform discussion, not the post-feedback re-approval gate).
• ExitPlanMode approval card shows stale plan content within a session #82369 — approval card shows stale plan content (card appears but is wrong; here no card appears at all).
• [FEATURE] Keep plan visible after requesting changes #33550 (closed) — "Keep plan visible after requesting changes" (visibility of the old plan; this report is about the revised plan never being surfaced or re-approved).

The severity here is the missing second approval gate, not only the missing display: choosing the most cautious option silently drops the permission checkpoint that options 1 and 2 both honor.