The New Pricing Model for Pro makes 0 sense - Make a new one

Feature Requests
1

I understand putting a limit in Claude 4.0 and 3.7 is logical. But reaching a limit and putting API pricing on all models makes 0 sense. All other AI platforms give us as many prompts to their older models as we reasonably want.

We should just have a limit on each recent LLM models.
Reaching a limit and locking all the models including the old ones doesn’t make sense at all, and you expect us to go with it when we have had the old models available to us all this time without limit.

This is a huge downgrade, and it is affecting the community.
Please review the Pricing Model and create something reasonable. We can incorporate elements from both the old and new pricing models, such as making older LLM models always available and implementing API pricing when the limit is reached on the more recent ones.

Thank you,
António

4 Likes
2

Yeah This has turned into an absolutely unusable mess. Every single time “auto” touches my code I spend the rest of the day trying to fix it. We had a nice thing and now its just ■■■■.

1 Like
3

Honestly, Cursor is becoming unusable.

The old 500 requests/month for any model was fair. Now it’s 225 for top model? Seriously?

Add the hidden API markup and lack of clear limits — and it just feels like we’re being milked. Loved Cursor before, but this pricing model is killing it.

Hope they rethink it before more users leave.

1 Like
4

I asked them to roll back to Old Pricing, and they did it. But I’m considering starting to use the Kilo Code extension on VS Code connected to the Claude Code CLI. Seems like the best of both worlds.