[BUG] ExitPlanMode skips approval prompt and displays false 'User has approved your plan' message (v2.1.63 regression)

Resolved 💬 13 comments Opened Feb 28, 2026 by pguillory Closed Mar 5, 2026

Preflight Checklist

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

What's Wrong?

In v2.1.63, ExitPlanMode intermittently skips the approval/reject dialog entirely and immediately returns "User has approved your plan. You can now start coding." The user never sees a prompt and never approves anything — the message displayed is factually incorrect.

When this happens, two things break:

  1. The approval prompt is never shown — the user has no opportunity to review, approve, or reject the plan
  2. The context clear that normally follows approval does not fire

This is intermittent. A minimal reproduction (fresh session, "call the ExitPlanMode tool") sometimes shows the prompt correctly. But in real planning workflows — entering plan mode, writing a plan, then calling ExitPlanMode — the prompt is frequently skipped and the false approval message is displayed.

Regardless of whether the approval prompt behavior was an intentional change: displaying "User has approved your plan" when the user took no action is incorrect. The user did not approve the plan.

What Should Happen?

ExitPlanMode should present the plan to the user with an approve/reject prompt, wait for their input, and on approval clear the conversation context (as it did in v2.1.62 and earlier).

Steps to Reproduce

  1. Start a session and enter plan mode (via EnterPlanMode)
  2. Explore the codebase and write a plan to the plan file
  3. Call ExitPlanMode
  4. Observe: sometimes the approval prompt appears correctly, sometimes it is skipped entirely and the tool immediately returns "User has approved your plan" with no user interaction

The bug does not reproduce 100% of the time in minimal cases, but occurs frequently in real planning workflows with significant context.

Is this a regression?

Yes, this worked in a previous version.

Last Working Version

2.1.62

Claude Code Version

2.1.63 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

Observed the transition cleanly in session transcripts from the same evening. Sessions running on v2.1.62 showed the approval dialog correctly every time. Sessions minutes later on v2.1.63 began auto-approving without prompting. The context clear (which was previously triggered by a meta message injection after approval) also stopped occurring.

View original on GitHub ↗

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