Auto Usage on Legacy Annual Individual Plans

Discussions
1

Today we fixed a bug that impacted a small subset of users on legacy annual individual plans purchased before September 15, 2025. The bug caused Auto usage to draw from the API usage pool (beginning on May 1, 2026) instead of the Auto pool.

We identified the source of the bug and have patched it going forward. This affected a very small slice of users: specifically, certain annual individual plan users whose plans should still have unlimited Auto honored until their renewal date in 2026.

If you believe you’ve been impacted, please reach out to [email protected] from the email associated with your Cursor account and mention “unlimited auto” in your email. We’ll review your account and help on an individual basis.

We appreciate your patience. While we’re monitoring and responding here, we’ll be able to help you faster through [email protected].

6

I’ve been affected by this bug for two consecutive months and only refunding one month is already a joke by itself. Next to that, it seems that since the changes have been made, “auto” on legacy plans seems to only use composer 2.5 and nothing else. this would be a violation of the terms agreed to so how about you give us the possibility to see which kind of models were used for legacy auto.

8

Hi @cyborg31 Can you share your Cursor email with me and I can take a closer look at your account?

9

I would love to but have not found a way to write a personal message.

10

Created a DM with you, I think you can respond now. Please lmk if so :smiley: