Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Code exited planning mode without my approval [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49557•Fetched 2026-04-17 08:37:45
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
nebriusnebrius
Participants
github-actions[bot]github-actions[bot]nebriusnebrius
Timeline (top)
labeled ×3closed ×1commented ×1

Error Message

Error Messages/Logs

Code Example

I asked Claude to explain how it got there, and here's what it said:

> The "Tell Claude what to do instead" input was routed back to me as a regular user message, but the system also emitted the "User has approved your plan" reminder. So the harness treated your inline comment as a full acceptance with edits, even though your intent was "I'm giving you feedback, keep planning."

> That's a genuine UX/plumbing bug — the "Tell Claude what to do instead" affordance on the approval dialog shouldn't be indistinguishable from "accepted with notes." Worth filing at https://github.com/anthropics/claude-code/issues with this screenshot; it's a clear repro.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

I was iterating on a plan with Claude Code via the VS Code plugin in VS Code (not via the integrated terminal), and I entered some text into "Tell claude what to do instead" when it prompted me to accept a plan. Claude then exited plan mode and started implementing.

What Should Happen?

Claude code should not exit plan mode unless a plan is approved.

Error Messages/Logs

I asked Claude to explain how it got there, and here's what it said:

> The "Tell Claude what to do instead" input was routed back to me as a regular user message, but the system also emitted the "User has approved your plan" reminder. So the harness treated your inline comment as a full acceptance with edits, even though your intent was "I'm giving you feedback, keep planning."

> That's a genuine UX/plumbing bug — the "Tell Claude what to do instead" affordance on the approval dialog shouldn't be indistinguishable from "accepted with notes." Worth filing at https://github.com/anthropics/claude-code/issues with this screenshot; it's a clear repro.

Steps to Reproduce

The steps I took are clear, but it's the first time I've seen it, so it will likely be difficult to reproduce. Either way though, the UX plumbing should be such that anything other than an explicit approval is a rejection.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.111

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by treating any non-explicit approval as a rejection in the "Tell Claude what to do instead" input.

Guidance

  • Verify that the "Tell Claude what to do instead" input is not being treated as a regular user message, which could be causing the plan mode to exit prematurely.
  • Check the UX plumbing to ensure that the "Tell Claude what to do instead" affordance is distinguishable from "accepted with notes" to prevent similar issues.
  • Consider filing an issue with a screenshot to document the problem, as suggested by the error message.
  • Review the approval dialog to ensure that it clearly indicates when a plan is being approved or rejected.

Example

No code snippet is provided as the issue is related to UX plumbing and not a specific code error.

Notes

The issue may be difficult to reproduce, and the root cause is related to the UX design rather than a specific code error. The provided error message suggests that it's a genuine UX/plumbing bug.

Recommendation

Apply workaround: Modify the UX plumbing to treat any non-explicit approval as a rejection in the "Tell Claude what to do instead" input, as this will prevent the plan mode from exiting prematurely.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING