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

Status Fixed / completed
Reported on v2.1.62
Maintainer reply None cached
Activity 13 comments · opened Feb 28, 2026 · 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 ↗

13 Comments

github-actions[bot] · 6 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/27265
  2. https://github.com/anthropics/claude-code/issues/29499

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

ZenAlexa · 6 months ago

Exactly, I encountered this same issue in 2.1.63 as well; the user's response is completely skipped, and the plan written by Claude is automatically approved directly.

mateusfig · 6 months ago

I confirm this same issue after updating the extension a few hours ago. The earlier version didn't have this issue.

Huntehhh · 6 months ago

I've been having the same issue As of yesterday.

mateusfig · 6 months ago
I've been having the same issue As of yesterday.

I downgraded to the last version to get it working again.

srinitude · 6 months ago

Confirmed regression! Also downgraded

@ThariqS @bcherny

srinitude · 6 months ago
Confirmed regression! Also downgraded @ThariqS @bcherny

Feel so much better after dropping down to 2.1.62

mateusfig · 6 months ago

I can't see the 2.1.62 in VSCode

<img width="257" height="279" alt="Image" src="https://github.com/user-attachments/assets/98737ec0-59f4-49f1-b588-667751e14afc" />

srinitude · 6 months ago

Ah, I'm working from Claude Code CLI in Warp terminal

ZenAlexa · 5 months ago

No fix in 2.1.66.

ZenAlexa · 5 months ago

No fix in 2.1.68

pguillory · 5 months ago

Appears to be fixed in 2.1.69.

github-actions[bot] · 5 months ago

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.