claude-code - 💡(How to fix) Fix [BUG] - Claude Code in Cursor implements in edit automatically mode even though Plan mode is turned on [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#52992Fetched 2026-04-25 06:15:18
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×5commented ×1

Error Message

Error Messages/Logs

Root Cause

I'll report it, because the plan indicator was definitely toggled on Helpful details to include in the report so they can 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 switched to plan mode in Cursor, and instead of operating in plan mode, CC just proceeded in edit automatically mode. I had it diagnose itself. Here is what it reported: Most likely cause: when I called ExitPlanMode after you approved the first plan, Claude Code automatically exits plan mode. To go back into it, you have to actively re-enter (Shift+Tab cycles modes in the CLI; in the VSCode extension it's the mode selector near the input). If you toggled it but focus was elsewhere, or if it was toggled after the message was already submitted, the message would ship in normal mode with no plan-mode system-reminder attached — which is exactly what I saw on that turn (no reminder, so I proceeded).

Two quick ways to verify before your next "plan this" message:

Look at the mode indicator in Claude Code (status strip at the bottom of the terminal or the VSCode chat panel) — it shows "plan mode" in orange when active. Send a test message like "what mode are you in?" — I'll confirm from the system reminders I'm receiving. If the indicator says plan mode is on but my response shows I'm executing anyway, that'd be a Claude Code bug worth reporting at https://github.com/anthropics/claude-code/issues.

I'll report it, because the plan indicator was definitely toggled on Helpful details to include in the report so they can repro:

Environment: Claude Code VSCode extension on Windows 11 (since that's your setup). Repro sequence: enter plan mode → approve a plan via ExitPlanMode → wait for implementation to finish → send next message while the mode indicator still shows plan mode on → message arrives without the plan-mode system-reminder. Expected: system-reminder should be attached to every user message while the indicator shows plan mode. Hypothesis worth calling out: the issue may be tied to the automatic mode flip that fires when ExitPlanMode is called — if the indicator state and the backend state drift out of sync after that, the UI shows plan mode on but the message is sent in normal mode. Session timestamp: today, 2026-04-24, around the time of commit 4a644ac4. If you can grab a screenshot of the indicator showing "plan mode" while the conversation turn that got executed is visible, that's gold for the repro.

<img width="1464" height="1157" alt="Image" src="https://github.com/user-attachments/assets/43df1447-a6ae-4c0f-876f-7167b6e19235" />

What Should Happen?

See problem description - self explanatory.

Error Messages/Logs

Steps to Reproduce

In cursor:

  • Do something in plan mode, let it exit plan mode and go back to edit automatically
  • Switch back to plan mode
  • Give it some instruction
  • Watch it stay stuck in edit automatically even though you have plan mode toggled on

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.112 (Claude Code)

Platform

Other

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

No response

extent analysis

TL;DR

The issue can be fixed by ensuring that the plan mode is properly re-entered after it is automatically exited when ExitPlanMode is called.

Guidance

  • Verify the mode indicator in Claude Code to ensure it shows "plan mode" is active before sending a message.
  • Use the mode selector near the input in the VSCode extension or Shift+Tab in the CLI to re-enter plan mode after ExitPlanMode is called.
  • Test the mode by sending a message like "what mode are you in?" to confirm the system reminders are received.
  • If the issue persists, report it with the provided repro sequence and environment details.
  • Check the session timestamp and commit hash to ensure the issue is related to the current version.

Example

No code snippet is provided as the issue seems to be related to the UI and mode management in Claude Code.

Notes

The issue may be tied to the automatic mode flip when ExitPlanMode is called, causing the UI and backend state to drift out of sync.

Recommendation

Apply workaround: Re-enter plan mode manually after ExitPlanMode is called to ensure the mode indicator and backend state are in sync.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING