[BUG] After accepting a plan, Claude asks what to change instead of starting implementation

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

After entering plan mode and reviewing the plan, when I accept the plan (e.g. by saying "looks good, proceed" or pressing the accept action), Claude responds with a follow-up question asking "What would you like to change in the plan?" instead of exiting plan mode and beginning implementation.

The flow gets stuck in an infinite plan-review loop — the plan is never executed even after explicit acceptance.

What Should Happen?

After the user accepts the plan, Claude Code should exit plan mode and immediately begin implementing the plan (i.e., start making file edits, running commands, etc.).

Error Messages/Logs

No explicit error message. Claude simply responds with:

What would you like to change in the plan?

...after the user has already accepted it.

Steps to Reproduce

1. Start Claude Code in a project directory
2. Enter plan mode (via /plan or shift+tab to enter plan mode)
3. Describe a task — Claude generates a multi-step plan
4. Accept the plan (e.g. type "looks good, go ahead" or "accept" or use the accept keybinding)
5. Expected: Claude exits plan mode and starts implementing
6. Actual: Claude responds with "What would you like to change in the plan?" and stays in plan mode

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Not sure — noticed in v2.1.75

Claude Code Version

2.1.75

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

The bug appears to affect the plan acceptance flow specifically — the model either isn't correctly receiving the "accept" signal or is misclassifying an acceptance response as a change request. This makes plan mode unusable for hands-free implementation since the user must manually exit plan mode and re-describe the task.