This is a known issue. Planning mode sometimes ignores its limits and starts making code changes directly. This isn’t specific to Composer 1.5 or the CLI. We’ve seen similar reports across different models and setups.
A few workarounds that might help:
Start a new chat when switching to planning mode, especially after a long conversation. In long threads, the model is more likely to lose the planning mode constraint.
If you need to change an existing plan, try rephrasing your request to clearly ask for a plan update, like “update the plan to include X,” instead of wording that could be read as a request to take action.
Hey, sorry for the delay. The workarounds I mentioned don’t always help, and that’s a fair point.
This issue is still open on our side. The team knows that Plan mode doesn’t reliably follow its read-only limits, especially in longer conversations. We don’t have an ETA for a fix yet, but your report helps us prioritize it.