Plan mode tried to edit files #2102

Open
opened 2026-02-16 17:34:10 -05:00 by yindo · 4 comments
Owner

Originally created by @NaikSoftware on GitHub (Oct 14, 2025).

Originally assigned to: @rekram1-node on GitHub.

Plan mode created several points, and when tried to generate more plan items, it asked me to create implementation just during the planning phase

Image

I expect to see and verify the plan and then implement it. Faced with this issue several months ago and nothing has changed.

Originally created by @NaikSoftware on GitHub (Oct 14, 2025). Originally assigned to: @rekram1-node on GitHub. Plan mode created several points, and when tried to generate more plan items, it asked me to create implementation just during the planning phase <img width="2048" height="772" alt="Image" src="https://github.com/user-attachments/assets/aea23935-6b73-4a11-83ee-472060c4ceb8" /> I expect to see and verify the plan and then implement it. Faced with this issue several months ago and nothing has changed.
Author
Owner

@github-actions[bot] commented on GitHub (Oct 14, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #3038: The model loops attempting to edit files in PLAN mode - This issue describes the exact same behavior where the model tries to edit files while in planning mode instead of staying in plan-only mode
  • #3146: READ-ONLY Plan - While this mentions read-only mode specifically, it's also about unexpected plan mode behavior

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Oct 14, 2025): This issue might be a duplicate of existing issues. Please check: - #3038: The model loops attempting to edit files in PLAN mode - This issue describes the exact same behavior where the model tries to edit files while in planning mode instead of staying in plan-only mode - #3146: READ-ONLY Plan - While this mentions read-only mode specifically, it's also about unexpected plan mode behavior Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Oct 14, 2025):

yeah it's pretty annoying how the llm always tries to break free of the guardrails

the only foolproof way to fix is to remove the bash tool during planning but that tool can be helpful

Alternatives:

  • prompt iteration
  • try to automatically block common bash tool abuses with cat & sed for file edits
@rekram1-node commented on GitHub (Oct 14, 2025): yeah it's pretty annoying how the llm always tries to break free of the guardrails the only foolproof way to fix is to remove the bash tool during planning but that tool can be helpful Alternatives: - prompt iteration - try to automatically block common bash tool abuses with cat & sed for file edits
Author
Owner

@berenar commented on GitHub (Oct 29, 2025):

Hey @NaikSoftware, this should be fixed

@berenar commented on GitHub (Oct 29, 2025): Hey @NaikSoftware, this should be fixed
Author
Owner

@NaikSoftware commented on GitHub (Oct 29, 2025):

@berenar thank you, will test it in the next several days

@NaikSoftware commented on GitHub (Oct 29, 2025): @berenar thank you, will test it in the next several days
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2102