Hey, thanks for the feedback. Here’s how it works: on the legacy Pro plan (request-based), Grok 4.5 is only available in Max Mode. That’s expected behavior for request-based plans, not a setting we can toggle. Max Mode is billed by tokens, so the cost can be high.
On the new usage-based plans, Grok 4.5 is available without mandatory Max Mode. Billing is based on actual token usage, so you can use the model more flexibly. More details on models and pricing are here: Models & Pricing | Cursor Docs
Hey, thanks for laying this out in detail. I passed your feedback about Grok 4.5 pricing on legacy request-based plans to the team.
Just to confirm the mechanics again so there’s no confusion: on legacy request-based plans (this includes the old Pro and Team on request-based), Grok 4.5 is only available in Max Mode, and it’s not a toggle we can turn off on our side. Max Mode is billed by tokens, which is why the usage is high.
On the new usage-based plans, Grok 4.5 works without requiring Max Mode, and billing is based on actual token usage, so you can use the model much more flexibly. Details on models and pricing: Models & Pricing | Cursor Docs
On the compromise point, I hear you and I’ve passed your position along. I can’t promise changes or timelines, but if anything changes there, I’ll reply here.