Cursor removed cost information from the usage page and CSV export

aroman wrote: post #5

I was an early and passionate adopter and paying customer of Cursor (since 2023!), but it’s probably been 6 months since I opened it. These days I “write” code with claude code and codex, and read/review it on GitHub. If I need to read it locally, I use a plain text editor. Can someone help me understand what value cursor offers in 2026?

Recently they also seem to have made big changes that makes Cursor worse for editing code by hand. I'm not sure what they are trying to do, but it doesn't feel like vscode fork anymore. I'm starting to consider alternatives.

To answer your question though, to me your workflow seems cumbersome. Cursor is more integrated and more frictionless.

Re: Cursor removed cost information from the usage page and CSV export

#8

Post by slashdave » Sat, Aug 01, 2026, 4:27 PM UTC

Cursor achieved fast adoption by making it simple to move from Visual Studio code.

Double-edged sword. It is also simple to move back to VS code and agent extensions.

Re: Cursor removed cost information from the usage page and CSV export

#9

Post by btown » Sat, Aug 01, 2026, 4:29 PM UTC

I am shocked, shocked, that a company that is part of SpaceXAI would become hostile to its existing paying users and partners. This has never happened before in history.

Re: Cursor removed cost information from the usage page and CSV export

#10

Post by redox99 » Sat, Aug 01, 2026, 4:32 PM UTC

aroman wrote: post #5

I was an early and passionate adopter and paying customer of Cursor (since 2023!), but it’s probably been 6 months since I opened it. These days I “write” code with claude code and codex, and read/review it on GitHub. If I need to read it locally, I use a plain text editor. Can someone help me understand what value cursor offers in 2026?

Cursor has two benefits

1) It's still an IDE. Because of pricing I mostly use Codex, but I always have a VSCode/Cursor IDE open, thus have to juggle between the two. Working directly in the IDE is more comfortable. For full on vibecoding that might be worse, but when you want to do a deep review of the changes, an IDE is way better than reading a diff on github.

2) It supports every model. It's often very helpful to try different models when you don't like the result of the first.