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…
Cursor removed cost information from the usage page and CSV export
91–100 of 172 posts
Re: Cursor removed cost information from the usage page and CSV export
#92Earlier quoted context omitted.
How do you diff ? Unless by "text editor" you mean Neovim or Emacs ?
Sounds like on GitHub. That's how I do it too.
Diffing through a web interface offered by GitHub or Bitbucket is such a narrow window into changes.
Re: Cursor removed cost information from the usage page and CSV export
#93Re: Cursor removed cost information from the usage page and CSV export
#94Earlier quoted context omitted.
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…
Can't VS Code extensions solve your use case?
These days I've switched to Zed, which is good enough (and wicked fast), but I still miss Cursor as an IDE.
Re: Cursor removed cost information from the usage page and CSV export
#95Earlier quoted context omitted.
If they were smart, they'd rebrand Grok to Composer. Nobody wants to use the Nazi model.
please, you're dramatically overestimating who gives a shit about this.
And you're underestimating how much of a shit you need to give about this.
Re: Cursor removed cost information from the usage page and CSV export
#96Earlier quoted context omitted.
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…
> Claude Code injects a ton of tools into the system prompt 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
#97I 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…
Re: Cursor removed cost information from the usage page and CSV export
#98I 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. +-----------…
the "spamming" is mostly compaction appending files, tool artifacts, images in its summary there is a known github issue for codex. only solution is periodic clean up but its also how a lot of the agentic orchestration is performed and able to work for days.
Re: Cursor removed cost information from the usage page and CSV export
#99Re: Cursor removed cost information from the usage page and CSV export
#100I 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.
Should the AI sidebar be on the left, or on the right? At some point they swapped them automatically, which was jarring (maybe a bug). But now I realize that if I'm not the one primarily writing code and navigating it, then I prefer agents in the "primary" position on the left (esp. if I have the browser on the left half of the screen, the agents are in the middle).
What annoys me the most about Cursor is the random stuff that breaks (due to its nature of VS Code fork).
The tab experience is still unparalleled. The cost might be worse than Codex/Claude sub, but they are all much, much, much cheaper than API pricing, so depends on your POV.