Inconsistent Plan Mode Output: Missing Interactive Execution Prompt
Bug Description
I'm reporting an issue with inconsistent behavior in plan mode.
Expected Behavior:
When using plan mode, the final output should always be a structured, executable plan that presents the user with an interactive prompt for approval (e.g., a Yes/No choice). This should be the consistent behavior regardless of the request.
Actual Behavior:
Sometimes, instead of generating the actionable plan prompt, Claude Code simply describes the intended plan as plain text within its conversational response. The user can read the steps of the plan, but there is no prompt to approve and execute them directly.
Impact:
This inconsistency significantly diminishes the user experience of plan mode. It forces the user to guess whether they will receive an actionable plan or just a text description. When the latter happens, it breaks the workflow, as the user then has to manually copy the steps and re-prompt, which defeats the entire purpose of having an automated, approvable planning feature.
A consistent and reliable output format is crucial for plan mode to be effective.
Thanks for looking into this.
Environment Info
- Platform: darwin
- Terminal: iTerm.app
- Version: 1.0.24
- Feedback ID: 9fde3d4d-10ca-4633-8cad-dd11e9b43f18
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗