4 ms·

Cursor has been my main AI tool for over a year now. I've been trying to use Claude Code seriously for over a month, but every time I do it, I get the impressi

Cursor has been my main AI tool for over a year now. I've been trying to use Claude Code seriously for over a month, but every time I do it, I get the impression that it would take me less work to do with Cursor. I'm on the enterprise plan, so it can get pricey. This is why I used to stick mostly to auto mode. Now Composer 2 has taken over as my default model. It is not as intelligent as OpenAI's or Anthropic's flagship models, but I feel it has as good as or better intuition. With way better pricing. It can get stuck in more complex tasks though. Being able to get in the loop, stop and instruct or change models makes all the difference. And that is why I've stayed in the editor mode until now. Let's see if 3.0 changes that.

muratsu 6mo ago
I find it interesting that you are on the enterprise plan and are not default willing to pay more for more intelligence. Most people I know who are on the enterprise plan are wishing there existed a 2x intelligent model with 2x price.
- dakolli 6mo ago
  Because they are twice as stupid.
- athoscouto 6mo ago
  2x intelligence != 2x results most tasks I can do better and faster with composer 2 a fellow engineer reported a bug on a code I had written a few months back. I used his report as prompt for composer 2, gpt-5.4-high and claude-4.6-opus-max-thinking. composer found the issue spot on. gpt found another possible vector a couple of minutes later, but a way less likely one and one that would eventually self heal (thus not actually reproducing what we observed on production). claude had barely started when the other two had finished also, i don't have a budget per se. but it is expected that i over deliver if i'm over spending
- Jcampuzano2 6mo ago
  My company is going through the exact opposite, so it kinda depends on the company. We are actively encouraging our devs to NOT use Cursor because of how much more expensive it is compared to other tools we have from our calculations and they even considered dropping Cursor at contract renewal altogether due to their costs being higher than other tools.
lordmoma 6mo ago
the only guy in my whose code has more problems than others is the one who who uses cursor, am I missing something?
dirtbag__dad 6mo ago
I was a Cursor loyal until I was spending around $2k a week with premium models and my team had a discussion about whether we’d want to use more Cursor over hire another engineer. We unanimously agreed we’d rather hire another team member. I’m more productive than ever but I’m burning out. Anyway, as a result, I switched to Claude Code Max and I am equally as prolific and paying 1/10th the price. I get my cake and to eat it, too. *Note there’s a Cursor Ultra, which at quick glance seems akin to Claude Code Max. Notice that both are individual plans, I believe I’m correct you benefit from choosing those token-wise over a team or enterprise plan? Anyway, you’re right Claude Code is less ergonomic; generally slower. I was losing my mind over Opus in Cursor spinning up subagents. I don’t notice that happen nearly as frequently in Claude Code itself. I think it has to do with my relatively basic configuration. CC keeps getting better the more context I feed it though, which is stuff like homegrown linters to enforce architecture. All to say, Cursor’s pricing model is problematic and left a bad taste in my mouth. Claude Code seems to need a bunch of hand holding at first to be magical. Pick your poison
- sbysb 6mo ago
  > Anyway, you’re right Claude Code is less ergonomic; generally slower. The secret in my experience is parallelization - Cursor might be faster or have better ergo for a single task, but Claude Code really shines when you have 6 tasks that are fairly independent. If you treat CC as just another terminal tool and heavily use git worktrees, the overall productivity shoots through the window. I've been using a tool called Ouijit[1] for this (disclosure: the dev is an old colleague of mine), and I genuinely do not think I could go back to using Cursor or any other traditional IDE+agent. I barely even open the code in an editor anymore, primarily interacting through the term with Vim when I need to pull the wires out. [1]: https://github.com/ouijit/ouijit https://github.com/ouijit/ouijit
  - athoscouto 6mo ago
    Cursor can do that well too. Their code review feature usually gives a handful of independent feedbacks. I just trigger agents independently for all of those. Other integrations with Linear and Slack are also very handy to getting into this workflow. Seems like the 3.0 version is aiming at getting better at this use case.
thefourthchime 6mo ago
The workflow that got me into Cloud Code was instructing it that whenever I create a new feature or bug, it should make a new git worktree. And then when I'm done, merge that back to main and delete the worktree. That enables me to open up three plus different Cloud Code's and work on three different things at the same time. As long as they're not directly overlapping, it works great.

muratsu 6mo ago

I find it interesting that you are on the enterprise plan and are not default willing to pay more for more intelligence. Most people I know who are on the enterprise plan are wishing there existed a 2x intelligent model with 2x price.

dakolli 6mo ago
Because they are twice as stupid.
athoscouto 6mo ago
2x intelligence != 2x results most tasks I can do better and faster with composer 2 a fellow engineer reported a bug on a code I had written a few months back. I used his report as prompt for composer 2, gpt-5.4-high and claude-4.6-opus-max-thinking. composer found the issue spot on. gpt found another possible vector a couple of minutes later, but a way less likely one and one that would eventually self heal (thus not actually reproducing what we observed on production). claude had barely started when the other two had finished also, i don't have a budget per se. but it is expected that i over deliver if i'm over spending
Jcampuzano2 6mo ago
My company is going through the exact opposite, so it kinda depends on the company. We are actively encouraging our devs to NOT use Cursor because of how much more expensive it is compared to other tools we have from our calculations and they even considered dropping Cursor at contract renewal altogether due to their costs being higher than other tools.

lordmoma 6mo ago

the only guy in my whose code has more problems than others is the one who who uses cursor, am I missing something?

dirtbag__dad 6mo ago

I was a Cursor loyal until I was spending around $2k a week with premium models and my team had a discussion about whether we’d want to use more Cursor over hire another engineer. We unanimously agreed we’d rather hire another team member. I’m more productive than ever but I’m burning out. Anyway, as a result, I switched to Claude Code Max and I am equally as prolific and paying 1/10th the price. I get my cake and to eat it, too. *Note there’s a Cursor Ultra, which at quick glance seems akin to Claude Code Max. Notice that both are individual plans, I believe I’m correct you benefit from choosing those token-wise over a team or enterprise plan? Anyway, you’re right Claude Code is less ergonomic; generally slower. I was losing my mind over Opus in Cursor spinning up subagents. I don’t notice that happen nearly as frequently in Claude Code itself. I think it has to do with my relatively basic configuration. CC keeps getting better the more context I feed it though, which is stuff like homegrown linters to enforce architecture. All to say, Cursor’s pricing model is problematic and left a bad taste in my mouth. Claude Code seems to need a bunch of hand holding at first to be magical. Pick your poison

sbysb 6mo ago
> Anyway, you’re right Claude Code is less ergonomic; generally slower. The secret in my experience is parallelization - Cursor might be faster or have better ergo for a single task, but Claude Code really shines when you have 6 tasks that are fairly independent. If you treat CC as just another terminal tool and heavily use git worktrees, the overall productivity shoots through the window. I've been using a tool called Ouijit[1] for this (disclosure: the dev is an old colleague of mine), and I genuinely do not think I could go back to using Cursor or any other traditional IDE+agent. I barely even open the code in an editor anymore, primarily interacting through the term with Vim when I need to pull the wires out. [1]: https://github.com/ouijit/ouijit https://github.com/ouijit/ouijit
- athoscouto 6mo ago
  Cursor can do that well too. Their code review feature usually gives a handful of independent feedbacks. I just trigger agents independently for all of those. Other integrations with Linear and Slack are also very handy to getting into this workflow. Seems like the 3.0 version is aiming at getting better at this use case.

thefourthchime 6mo ago

The workflow that got me into Cloud Code was instructing it that whenever I create a new feature or bug, it should make a new git worktree. And then when I'm done, merge that back to main and delete the worktree. That enables me to open up three plus different Cloud Code's and work on three different things at the same time. As long as they're not directly overlapping, it works great.