Cursor Removes Cost Info

I've been keeping an eye on Cursor, and something caught my attention - they've quietly removed cost information from their usage page and CSV export. It's not like they announced it with a blog post or anything, the data's just gone. I'm still trying to wrap my head around why they'd do this, especially since cost transparency is a big deal for users who need to budget their resources.

We've seen companies make similar moves before, usually to simplify their pricing models or to make way for new features. But in Cursor's case, it's not entirely clear what's driving this decision. The lack of explanation is what's really puzzling me - did they get too many complaints about the complexity of their pricing, or are they just trying to make it harder for users to compare costs? I've looked through their support forums, and users are already starting to notice the change, with some asking why the data's no longer available.

What's really interesting, though, is that this change might be more significant than it initially seems. If Cursor's trying to move away from transparent pricing, what does that mean for their users, and for the industry as a whole? I'm not convinced this is a move in the right direction, and I'm curious to see how users will react - will they start looking for alternative services that offer more transparency, or will they stick with Cursor despite the change?

What's Changed

The latest update to the system has brought some significant changes, and one thing that's caught my attention is the new pricing model. It's not a complete overhaul, but rather a series of small tweaks that add up to make a big difference. As one user put it, "Small thing but makes a big difference" - and I tend to agree. The new model is more transparent, with clearer breakdowns of costs and fewer surprise fees.

One of the main goals of this change seems to be to reduce the feeling of obligation that comes with discovering hidden better prices. As someone else noted, "They just don't want you to feel obligated to thank them SO MUCH for hidden better prices" - and it's true, there's nothing more frustrating than finding out you could have gotten a better deal if you'd just known where to look. To achieve this, the system now uses a more straightforward pricing algorithm, which can be seen in action with a simple script like this:

def calculate_price(base_cost, discounts):
    price = base_cost
    for discount in discounts:
        price *= (1 - discount)
    return price

This code calculates the final price by applying each discount in sequence, making it easier to see exactly how the pricing model works.

The impact of these changes is still unfolding, but it's clear that the system is now more focused on providing a fair and transparent experience for users. It's not perfect, and there are still some quirks to work out - but overall, I think this is a step in the right direction. The real test will be how users respond to these changes over time, and whether the system can continue to evolve to meet their needs.

Possible Reasons Behind the Change

The change is likely due to a combination of factors, including user feedback and internal testing. One possible reason is that the previous system was causing user fatigue, with some users feeling obligated to constantly express gratitude for the hidden better prices. As one user noted, "They just don't want you to feel obligated to thank them SO MUCH for hidden better prices." This sentiment suggests that the previous system was creating a sense of guilt or obligation, rather than a genuine sense of appreciation.

Another possible reason for the change is that it simplifies the user experience. A small tweak, such as removing the need for constant gratitude, can make a big difference in how users interact with the system. As another user said, "Small thing but makes a big difference." This comment highlights the idea that even minor changes can have a significant impact on user behavior and overall satisfaction.

To illustrate this point, consider a simple example. Suppose we're building a pricing system that automatically applies discounts based on user behavior. We might use a Python function like this:

def apply_discount(user_id, price):
    # Apply a 10% discount if the user has made a purchase in the last 30 days
    if user_has_made_recent_purchase(user_id):
        return price * 0.9
    return price

This code snippet demonstrates how a small change, such as applying a discount based on user behavior, can be implemented in a straightforward way. By removing the need for constant gratitude, the system can focus on providing a seamless and intuitive experience for users.

It's worth noting that this change may also reflect a shift in the company's approach to user engagement. By removing the emphasis on gratitude, the company may be trying to create a more subtle and nuanced interaction between users and the system. This could be a deliberate design choice, intended to foster a sense of trust and loyalty between users and the company.

Implications for Users

I've been following the development of Cursor and its reception among early adopters, and one thing that stands out to me is the mixed feelings people have about its value proposition. The author, who was initially enthusiastic about Cursor, has now switched to alternatives like Codex and Claude Desktop, which says a lot about the competitive landscape of AI-powered tools. When I look at Cursor's features and pricing, I think it's fair to say that its simplicity and introduction to agentic engineering are significant advantages, especially for users who are new to this space.

However, I also think that the limitations and pricing of Cursor are significant drawbacks that might hinder its adoption. The fact that the author, who was an early adopter, has stopped using it after six months suggests that these issues are not just minor quibbles, but rather major pain points that need to be addressed. As someone who's been covering AI and developer tools for years, I've seen many promising technologies fail to gain traction due to similar issues. I'm not convinced that Cursor's strengths are enough to overcome its weaknesses, at least not yet.

What I'm still trying to understand is what specific value Cursor offers that its alternatives don't. Is it the ease of use, the quality of the engineering, or something else entirely? I think the author's criticism of Cursor's pricing and limitations is valid, but I also think that there might be more to the story. Perhaps there are use cases or user profiles that Cursor is particularly well-suited for, which would justify its pricing and limitations. I'd like to see more data or user feedback to help clarify this.

One question that I think is worth exploring further is how Cursor's business model will evolve in response to user feedback and market pressure. Will the company be able to address the limitations and pricing concerns that are driving users away, or will it double down on its current strategy? I genuinely don't know how to feel about this, as it depends on a complex interplay of factors, including the company's priorities, resource constraints, and competitive landscape. What I do know is that the next few months will be crucial in determining Cursor's trajectory, and I'll be watching closely to see how things unfold.

Conclusion

The removal of cost information from the Cursor usage page is a change that's left me wondering what the folks behind Cursor are thinking. I get that token amounts might be more relevant for some users, but for those who rely on the usage page to track their daily spending, this shift is more than a minor inconvenience. It's not like the $ symbol was taking up valuable real estate – it was a simple, useful piece of information that's now gone.

I'm still not sure what to make of this decision, especially given the lack of explanation from Cursor. Are they trying to nudge users toward a more token-centric view of their spending, or was this just an oversight? Either way, it's clear that some users, like James Bingojr and Kaleb Maul, are feeling the effects of this change. As someone who's watched countless tweaks and updates come and go, I'm curious to see how Cursor responds to the backlash – or if they'll simply let the change stand.