[Bug] Plan mode modifies files despite planning mode being enabled
Status Closed — not planned
Reported on v2.1.31
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 6 comments · opened Feb 4, 2026 · closed Apr 2, 2026
Bug Description
was in plan mode but it changed the file either way
Environment Info
- Platform: darwin
- Terminal: kitty
- Version: 2.1.31
- Feedback ID: 3ca7be59-2136-42bb-9c46-315b1fa929e3
(keep in mind this session is old so the first error messages might not be relevant)
Errors
[{"error":"Error: 500 {\"type\":\"error\",\"error\":{\"type\":\"api_error\",\"message\":\"Internal server error\"},\"request_id\":\"req_011CXoMyJYrrJTTZrpAifF4D\"}\n at generate (/$bunfs/root/claude:344:8942)\n at makeRequest (/$bunfs/root/claude:361:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:42:05.949Z"},{"error":"Error: 500 {\"type\":\"error\",\"error\":{\"type\":\"api_error\",\"message\":\"Internal server error\"},\"request_id\":\"req_011CXoMz83NKHU67mwqz9UpW\"}\n at generate (/$bunfs/root/claude:344:8942)\n at makeRequest (/$bunfs/root/claude:361:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:42:16.208Z"},{"error":"SyntaxError: JSON Parse error: Unexpected identifier \"API\"\n at <parse> (:0)\n at parse (unknown)\n at <anonymous> (/$bunfs/root/claude:70:855)\n at A (/$bunfs/root/claude:11:7248)\n at sX_ (/$bunfs/root/claude:761:91950)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:42:16.208Z"},{"error":"Error: Request was aborted.\n at zJR (/$bunfs/root/claude:1551:23586)\n at znB (/$bunfs/root/claude:5719:7546)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T18:44:01.157Z"}]
6 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
2.👍
Even when instructed "make a plan to do X" in plan mode, it will kick itself out of plan mode and start implementing.
This may have been caused by allowing edits outside of plan mode earlier in the session.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
Same here. I'm on v2.1.90 and made sure my CLI is fully up to date. I'm using Opus 4.6 with high effort in dangerous mode on Mac. Mine will actually make a plan in plan mode the first time, but once I approve the plan the mode indicator at the bottom of the terminal never changes out of plan mode. After that is does not plan any more, it just goes straight to build on every prompt. When I ask Claude about this it says that it signaled to exit plan mode when I approved the plan and it can confirm that it is not in plan mode, but it still says plan mode on my terminal and while shift-tabbing looks like it changes the modes, the agent/orchestrator has no idea that the mode changes. The only workaround right now is to exit and re-enter after each plan, since you can use plan mode once until you approve your first plan, then it is just stuck in bypass permissions mode.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.