Yes, me too.
After grok-4.5-xhigh was renamed/migrated to cursor-grok-4.5-high, the same underlying Grok 4.5 model consumes drastically more of my included usage — even though it used FEWER tokens. I did not enable fast mode.
From my Included Usage page, same billing period, First-party models:
- grok-4.5-xhigh: 21.0M tokens → 4.6% of quota
- cursor-grok-4.5-high: 16.4M tokens → 6.7% of quota
So cursor-grok-4.5-high used about 22% FEWER tokens but consumed about 46% MORE quota. That works out to roughly 1.85x higher cost per token, for what should be the same Grok 4.5 model at the same $2/$6 list price — and this is happening during the first-week double-usage promo, which should make it cheaper, not more expensive.
This clearly does not match the published pricing. Please clarify:
- Why does the same Grok 4.5 model bill so differently after the rename?
- Is prompt caching still active for cursor-grok-4.5-high? These numbers suggest it is not.
- Is this a billing regression introduced by the migration, and can the previous behavior be restored?