How to describe this situation?
Is Compound 2.5 too low-energy?
Why does cursor grok 4.5 automatically switch to plan mode under the same instruction, while compose 2.5 does not automatically switch to plan mode?
Moreover, during the chat process, cursor grok 4.5 will automatically switch to plan mode, while compose 2.5 will never automatically switch to plan mode!
I want to make it clear that compose 2.5 will never automatically switch to plan mode!
Did the agent not consider the situation of Compound 2.5?
I guarantee that Compound 2.5 has 100% no ability to automatically switch to Plan mode!
Steps to Reproduce
Use this command to verify:
Now please write down your MECE (mutually independent, completely exhaustive) design proposal, I will review it, and only after passing the review can you write/modify the code!
Hey, thanks for the report. One important detail: auto switching into Plan mode is a model decision. It decides whether to plan first based on your request and the context. Different models make different choices. Composer 2.5 is a faster, lighter model, so it more often jumps straight into action, while Grok 4.5 with the same instruction more often chooses planning. This is expected model behavior, not a bug.
If you need planning to happen every time no matter which model you use, turn on Plan mode manually using the mode toggle Shift+Tab or the mode selector next to the model picker. Then any model, including Composer 2.5, will write a plan first and wait for your review before changing code.
I’ll pass along your feedback about Composer 2.5 switching to Plan mode more proactively. Let me know if turning on Plan mode manually helps.
incorrect! You misunderstood!
I just don’t know how to describe it to you!
Even when I was using cursor grok 4.5 and compound 2.5, I had no idea that this issue would be automatically switched to plan mode by cursor grok 4.5! Is cursor grok 4.5 more intelligent?
Composer 2.5 does not have the ability to automatically switch to plan mode!
I was in agent mode and I didn’t know this issue would be automatically switched to plan mode by cursor grok 4.5! Is it due to the insufficient comprehension ability of Compound 2.5?
Thanks for clarifying, I think I understand you better now.
You’re right about what you’re seeing. With the same instruction, Grok 4.5 more often switches into Plan mode on its own, while Composer 2.5 usually jumps straight into action. But that doesn’t mean Composer 2.5 can’t do it. Auto switching to Plan is a model decision, not a separate feature that’s enabled for one model and disabled for another. Composer 2.5 can switch into Plan too and sometimes does, it’s just that Grok 4.5 is trained to be much more proactive about it. So “100% no capability” is more like “it chooses it much less often”, not that it’s missing entirely.
If you want planning to happen every time, regardless of the model, turn on Plan mode manually:
Shift+Tab or the mode toggle next to the model selector.
Then any model, including Composer 2.5, will write a plan first and wait for your review before changing code. You can also tell Composer in your request: “switch to Plan mode”, and it will do it.
I’ll pass your feedback to the team that you’d like Composer 2.5 to switch into Plan more often. Let me know if enabling Plan mode manually helps.