[BUG] Claude Code Web fully ignores plan changes and always approves original plan, plan mode switch broken
Resolved 💬 3 comments Opened Mar 23, 2026 by remixer-dec Closed May 24, 2026
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?
In the web version, I tried the "plan mode", noticed that it is extremely buggy:
- after Claude suggested the plan, I typed my edit suggestion in a text field bellow the "approve" button. I typed what I did not like about the plan, Claude completely ignored this text and proceeded implementing the original plan.
- I tried to ask Claude to suggest me a "test plan" so I can test the issue even more, but all the next "plans" were auto-approved without even asking me (see pic)
- Claude responds that "ExitPlanMode is erroring out — I'm not in plan mode. The first time it appeared to work was likely because the session started in plan mode (via /plan). Now that we've moved past that, it no longer works."
- The
plan modeswitch on the page is still active all this time. - In another session even when I turned the switch off in the middle of the session, it kept suggesting me new plan before implementing the changes
What Should Happen?
Claude should respect plan mode switch and suggested plan corrections, auto-approval should be fixed
Error Messages/Logs
Steps to Reproduce
Ask Claude Web to implement something in plan mode, then criticize it, look it if it changed anything, stop it, try again in response
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
claude 2.1.81 (Claude Code)
Platform
Other
Operating System
Other
Terminal/Shell
Other
Additional Information
<img width="734" height="755" alt="Image" src="https://github.com/user-attachments/assets/6b57a9e4-46ea-42f4-978d-d640009d9a51" />
Browser: Firefox (latest), mac os
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗