[Bug] ExitPlanMode never called after Write tool — plan not shown to user (3 consecutive failures)
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?
After EnterPlanMode + Write tool (PLAN.md), ExitPlanMode is never called. The plan is not displayed to the user. Even after pointing out the issue 3 times, Claude verbally acknowledged the mistake but still failed to call ExitPlanMode each time.
What Should Happen?
After EnterPlanMode + Write tool (PLAN.md), ExitPlanMode is never called. The plan is not displayed to the user. Even after pointing out the issue 3 times, Claude verbally acknowledged the mistake but still failed to call ExitPlanMode each time.
65e86f56-1cc6-4c04-91fb-74002366ec74.txt
Error Messages/Logs
No error messages displayed. Session silently stalled at "Waiting for input..." state after plan file was written. Debug log attached above.
Steps to Reproduce
- Open Claude Code Desktop (v1.1.3363, model: claude-opus-4-6)
- Ask Claude to plan a task: e.g. "Review these results and propose a plan"
- Claude calls EnterPlanMode
- Claude calls Write tool → creates PLAN.md successfully
- Claude's response ends here — ExitPlanMode is NOT called
- UI shows "Waiting for input..." — no plan is displayed to user
- User types: "Is it stuck?"
- Claude responds verbally: "Sorry, I should have called ExitPlanMode" — but does NOT call it
- Repeat steps 7–8 two more times → same result each time (3 total failures)
- Session only recovers after user presses Escape manually
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.1.3363
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
This bug occurs in Claude Code Desktop GUI, not in the terminal CLI.
The session was using plan mode (EnterPlanMode/ExitPlanMode tools).
Debug log file attached in the previous section.
Screenshot of the stuck session is also attached showing "Waiting for input..." state after plan file was written.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗