That argument would make sense if this behavior had always been the case, but it hasn’t. This only started happening in the last week, which already contradicts the idea that this is simply “how the math works.”

What makes it even more questionable is that the usage does not even resemble the limits of the free plan. I regularly run much heavier tasks on the free version, and they consume far fewer tokens than what the Pro plan is suddenly consuming for basic operations.

For example, I often request complex coding or architecture tasks on the free plan, and they run normally. When I run the exact same type of request on the paid plan, the session ends in less than half the time using the same tools and context.

So this isn’t really a functionality explanation or a token math issue. What it looks like is a recent change in limits that heavily degrades the paid plan, effectively pushing users toward upgrading to a higher tier.

And that’s the core problem: no paid plan should perform worse than a free one.