Earlier quoted context omitted.
What tools are you using to run the comparison? Or are you just running the prompts and checking them with something like ccusage? I’m asking because I’ve been looking for agent harness comparison tools too. I’m interested in more than just the inputs and outputs—I also want the system prompts, traces, and tool calls. It’s useful to understand why Codex, for example, uses more tokens while Pi doesn’t. Fewer tokens ar…
I built an ad-hoc custom comparison framework to inspect system prompts, caching behaviour, tool call outputs, exact api requests and responses and so on I agree fewer tokens is not necessarily better but a bit counter-intuitively often the harness using fewer tokens is not only done faster but has better results (that said: of course check the results, look at the full traces, agree!)
Cursor removed cost information from the usage page and CSV export
61–70 of 172 posts
Re: Cursor removed cost information from the usage page and CSV export
#62The ground-truth is the rudeness is load bearing at human machine interface.
Re: Cursor removed cost information from the usage page and CSV export
#63Kind of (barely) like how Facebook has "friends". Or how a Snickers bar costs $1.99 and not $2.
Abstracting meaning of "cost", reducing value of information. Maximizing profits. Enshittification.
Re: Cursor removed cost information from the usage page and CSV export
#64I can only recommend to regularly measure how many tokens a harness+model combination uses for a certain task There are huge token efficiency/bloat differences between agents while working on the same tasks, using the same model, in the same environment Yesterday I ran 10 agentic tasks using GPT 5.6 Sol in an ubuntu 26.04 vm a couple of times with different harnesses and got vastly different token usage. +-----------…
Claude Code injects a ton of tools into the system prompt, including their “memory system” that’s like 10k+ tokens. Depending on your task shape, this can easily double your task cost (e.g. a low context-using job that takes many turns, like a monitoring loop). You should use --disallowed-tools to prune any tools not needed for the task. Note that this is also a perpetual game of whack-a-mole since they’re always add…
It's so unfortunate they don't let you use the subscription with other harnesses anymore - since even if I used OpenCode they'd still get a bunch of useful data from the API calls, meanwhile I could stretch their tier limits way further.
Re: Cursor removed cost information from the usage page and CSV export
#65Cursor 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
#66Re: Cursor removed cost information from the usage page and CSV export
#67You can still see what you’re billed on the Spending page. We did accidentally break dollar costs in the Usage CSV export yesterday while cleaning up an old feature flag. That was not intentional and the CSV export is fixed now.
That feature flag also showed a dollar usage graph to some self-serve users. The confusing part was included plan usage shown as $, which is not what you’re billed (on-demand usage is). Some people read it as actual spend, so we decided to remove that graph.
Re: Cursor removed cost information from the usage page and CSV export
#68I 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?