upvote
I use cursor 8+ hours/day at work, and have full (and effectively unlimited) access to Claude Code and Codex - tools which I also use personally. I suspect that your "constant popups" were when you were using the editor - a mode that I'll confess I haven't touched in 3+ months.

Workflow in Cursor is actually awesome - I'm a little outdated in how I use it - I still establish goals/objectives, rather than managing the loop which does so - but if you can think broadly enough - I find it's pretty efficient.

Key things I like about Cursor (and I recognize I'm dating myself a bit here): - Plan Mode is really solid - I shift-tab, have it go create the plan using whatever insanely expensive SOTA model is available - I will usually spend 5-10 minutes on the Plan - review it, maybe even tweak it a little. (though 90% of the time it's fine out of the gate)

  - Ability to select any model for every task - I'll switch between Opus 4.8 High/xHigh/...  I'll even switch to 1M context for the planning phase upfront.   

  - It does an *excellent* job managing permissions and looping the agents and spinning up sub-agents for you - you set the goal, run the plan mode - and then let it churn for however long is required - pretty common to have a 30-45 minute run and come back to a fully created/tested product.   

   
The nice thing about Cursor (and honestly Claude Code, Codex) - there isn't really any "prompt engineering" involved. You just say, "Go Build me x - it should have y,z features - and build it in golang for me" - and that's it - the 3-4 page Plan comes back - usually pretty credible - and then you click "build.".
reply
But what's the $60B differentiator here? There are so many similar tools out there. I generally use Opencode, but also Claude code, antigravity and sometimes Kilo code on VS Studio. How can cursor be worth even 10% of 60B?
reply
> How can cursor be worth even 10% of 60B?

Maybe because SpaceX paid with monopoly money (all stock deal)?

reply
[delayed]
reply
There is most certainly still prompt engineering involved. How there can be both the responsivity to different cues like "plan this", "write this", "analyze this", "defend this", "poke holes in this", but not responsivity to the various terminology you provide in your explanations of "this", where to get information about specs/standards/requirements, what details I care about, and therefore can't compromise on, vs what details I'm willing to accept whatever the top reddit post from 4 years ago recommends.

I don't see how these systems can have the ability to be effectively expressive about all of the minutia, and not have all of the various different possible expressions lead to vastly different outcomes.

reply
I think all of the cues that you just described are in the plan.

For example - I might (real world example from this morning):

"Create a script that installs hashicorp vault and consul, store the data on consul. Then create ahelper script that will fill the vault server with sample data. Add HTTPS support. Now write a framework that reads and decrypts the encrypted data in consul. Support old (pre 1.3) and new (post 1.3 vault). "

That generates a 6 page plan using Opus 4.8 w/1mm context, including notes on what to prioritize, what format to create the scripts in, etc... (My cursor guidance already has a couple months of hints as to what I want in terms of scaffolding unit tests, canonical linux, performance, security, etc...)

That 6 page plan is the "Prompt" - but it's entirely generated by Cursor/Opus. It's there to tweak if you want to emphasize, or provide some taste - but, honestly - it probably does a better job than I would - so ~90% of the time I just accept the plan as is.

reply
Dunno, Cursor's agents are now more-less equal to Claude Code, just the workflow is slightly different. I like the IDE integration for some projects, allowing me to quickly inspect/review/change/search code, while running Claude Code/Codex/OpenCode/Pi/Hermes on different projects often with local models and it's mostly a question about your personal development style instead of inherent tool capabilities.
reply
Same.

When I first used Cursor, I hadn't used any of the "Vibe Code" tools out there, so it was pretty neat to have an assistant directly tied to the editor.

Once I learned how to use Codex, I just used a tmux split with NeoVim and have the effect I wanted. I haven't felt compelled to use Cursor at work since.

reply
I also work with C++, and I use Codex (desktop) which writes 99.99% of my code, plus Visual Studio, which is nice for reading and navigating code. For webdev I do VSCode + Codex.

I started with Cursor back in the day, but switched to Claude Code and then Codex when Cursor got too expensive.

If price wasn't an issue, maybe I'd prefer Cursor only because I can easily switch between models. But that's it. I always disliked the "accept/reject" workflow in cursor, but that's probably optional nowadays I guess?

reply
I love the accept reject flow because I still constantly have to stop AI models from writing awful architecture or reimplementing code we already wrote elsewhere
reply
Fable makes any IDE AI integration almost entirely unnecessary. Claude one shots pretty much everything, and fixing any small errors is easier when just talking to Claude again.

Anthropic is going to offer better pricing using their agentic harness. Why pay more for less?

An IDE at this point is best as a tool for code review. They need to start building better code review tools.

reply
the reason to use cursor nowadays isn't the IDE (though it's helpful perhaps once a week), but how it makes running models from multiple providers trivial out of the box. I don't have to juggle keys or drop to a shell tool call, it supports calling out to e.g. gemini in a subagent natively. I have multiple models cross-reviewing plans and diffs as a matter of course.

claude code was seriously annoying with the flickering, maybe it's fixed now, I don't know.

cursor also has a (bad) cli if you need it, it seems it's mostly used to setup remote agents, but it does the job in a pinch.

reply
For what it's worth, flickering in CC has been fixed since around the beginning of the year.
reply
I still saw a lot of flickering in VS Code (I simply use CC as a terminal in VS Code, without the plugin) as of 2 weeks ago. I think it's a combination of CC bugs + Electron(?) rendering the VS Code uses for terminal.

Moved on to Zed (native Rust rendering) 2 weeks ago -> nothing flickers.

Sadly, with Fable 5 cutoff, I am actively exploring CC alternatives. Pi/OMP.sh works great as an agent (definitely better than CC). GPT is seemingly not as good as Opus, but with better agent and better skills, it probaly won't matter anyway. GPT lets you use any agent on Pro subscription.

reply
Maybe flickering, but it's still broken in various ways. Only a few days ago I had an issue where the text I was typing was outside of the textbox frame. Resizing the terminal still maintained the broken view.
reply
OpenCode and Pi do those things as well, and without a whole annoying IDE bundled in.
reply
OpenCode is miserable from a security perspective. Well clarification the plans they offer where they bundled in free models that train on your use. You are then left to use an OpenRouter which I find pretty flaky for at least the leading Chinese models.
reply
I just use my ChatGPT subscription with it. Not sure what you mean about security.
reply
“Well clarification the plans they offer where they bundled in free models that train on your use.”

Just what I said. They offer paid plans through their tool. Said paid plans are kind of a dark pattern where it’s not immediately obvious the models are training on your data. The harness is fine but that kind of business turns me off and I am usually pretty neutral about those sorts of things.

reply
Yep in my experience the weakest engs in my org are the ones still using Cursor. not a good outlook IMO
reply
I know this is not always true. But the same people who like cursor still are the same people who are less familiar with the terminal.

And I don't know what it is but it feels the less familiar you are with a terminal, the less skilled you tend to be.

Definitely not a 100% case. But has been common in my experience

reply
I think it's more of a sign of a good engineer. I know a number of engineers that are good and don't really work with the terminal. On the other hand, every engineer I've worked with who was a 'terminal guy' was great. I think being good with the terminal is a signal that the person is willing to 'dig in' and understand stuff at a lower level.
reply
[dead]
reply
I strongly disagree with the parent commenter. I use cursor because it shows its thinking with more detail and much faster than Claude. That way, I can stop it in its tracks if went off the rails. Claude seems slow to me. No relation to engineering caliber.
reply
Totally disagree. I find people still using cursor or other IDE centric flows want to review the code and be more interactive. Claude Code and Codex push agent autonomy and speed. Sorry but they go off the rails too much.
reply
Cursor has a terminal based app that’s just as good as any of the other mainstream ones…
reply
why do annoying engineers have such a weird fetish/superiority complex about the terminal. Its an inherently inferior UI. Theres absolutely nothing you can do in a terminal that you cant do in a GUI, and every TUI is just jumping through insane hoops to support functionality thats trivial in a GUI.

Why on earth would you want to look at a code diff in a terminal? Why on earth would you want to use weird bespoke keyboard shortcuts to navigate sub-agents in a TUI session. Why on earth would i not want the ability to open/edit a file manually in the tool im using to write code.

can someone please explain this to me?

reply
Absolutely nothing? That's certainly not true. My experience is that those who grew up learning the command line are so familiar with it that they excel at navigating those bespoke keystrokes more quickly than any GUI user who has to scroll, point, and click. Add to that the ability to use a command history, and shell users are often far more productive than GUI users.
reply
As someone who has spent the last 10+ years working in Tmux - but is entirely comfortable on Mac, Windows and Linux desktop environments - here are the key reasons why the terminal experience is superior for me.

- I work a lot with data - and streaming data through text tools is twitch fast. If someone has a question about data - before anybody else can log in to their superset, or analytics database, and try and work through the SQL queries or charts to get the answer - I've already jammed the data through awk and got an answer.

- As an SRE - I work with a lot of systems that have pretty rich APIs - so being able to send a request, get the answer back in json, dump it into jq, select the parts I care about - maybe -c to compress it and ripgrep a subset out - is just fast.

- I work in a lot of contexts with a lot of different systems, datacenters, applications - tmux lets me keep all of them cleanly organized in a separate windows and subpanes. I'll have 15-20 windows open per week, and maybe a 5-6 panes in each- keeping 100+ different contexts (and scroll backs, bash history) - all nicely organized is really useful.

- I'm also a systems guy - and there is no other way to dig into a system but the terminal - netstat, ps, dmesg, /proc - these are all components that have only one credible path to investigation and discovery. If you aren't super comfortable in the terminal - zero way to learn about this stuff.

- Working remotely - means ssh. So - once again - terminal.

The Focus on the terminal is that it's the best tool (and in some cases the only tool) for so many of these tasks - and by performing these tasks a lot - you learn about systems - so the people who spend a lot of time in the terminal tend to know a lot more about systems than people who don't.

reply
Different strokes for different folks, but unfortunately they take their opinions and preferences as a sign that others are inferior.
reply
Yah this judgment and arrogance is so annoying in tech. And worse it stops us from learning. Some of the best lessons of my career were when a new developer asked a question often taken for granted or we implemented a design pattern to make coding more approachable.
reply
why do annoying engineers has such a weird fetish/superiority complex about the terminal. Its an inherently inferior UI. Theres absolutely nothing you can do in a terminal that you cant do in a GUI, and every TUI is just jumping through insane hoops to support functionality thats trivial in a GUI. And guess what, you can just open a terminal in cursor! who knew!?

Why on earth would you want to look at a code diff in a terminal? Why on earth would you want to use weird bespoke keyboard shortcuts to navigate sub-agents in a TUI session.

can someone please explain this to me?

reply
I am not one of them but quite a few programmers prefer not having to use the mouse at all when working.

The terminal is an old but astonishingly powerful user interface that is still evolving.

Good terminals can be very snappy and configurable in ways that most GUI are not.

There is also arguably an aesthetic/fetishism appeal to it.

I've worked in the terminal at some point of my career, as there was not many other choices, and I understand how someone can get really used to it.

reply
What's a polite way to suggest you ask AI first?

Why should others spend their valuable time helping you? Especially when you insult the people you want to answer you "fetish/superiority complex" just demonstrates your own prejudice.

Personally I ask AI for a summary of positions, and prompt to provide some good articles on a subject - ideally articles from supporters of either side.

reply
id prefer a human to explain it to me
reply
Speed and scriptability
reply
Honestly the TUI in most of these coding agents is so fancy I have trouble thinking of them as "terminal". I use Pi Coding Agent and the fact that it's terminal means it's easy to run inside something properly sandboxed in a YOLO mode using normal bash commands instead of relying on individually sandboxed tools.

Once I got the tmux settings for proper scrolling and whatnot it feels fine. Honestly the TUI of tmux is the one that really enrages me - so much complexity for just "I want to switch terminals on my remote".

reply
Opposite. The weakest engineers trust CC or codex, stopped reviewing the code and push slop PRs. Those still acting in the loop move faster with better architecture and coding patterns and aren't losing their skills.
reply
I don’t think mapping tooling to ability makes sense here, particularly when the “advanced” tools here just abstract more away, though I agree that Cursor is terrible. So many useless windows.
reply
deleted
reply
I hate to be the one to break it to you but the weakest engineers are going to be producing just as much value
reply
Same path as you. Went from $60 cursor plan (often exceeding it which costed more in API) to a limitless $100 codex plan where I basically say "read the markdown and implement the instructions". Deepseek also works quite well, surprisingly!

(FWIW Im mostly using python for OCR, LLM calls, data analysis..)

reply
Cursor also seems to be doing something with the Claude models that makes it way slower and less efficient as times goes by.

Or it could be just Claude CLI doing something very well.

reply
What are you saying is going to be over in a year or so?
reply
Right now I think there is an edge to how you construct prompts and config files. There is a large difference between "modify f() to do..." and "modify f() to do... Review the current variables and make sure they are still used consistent with their naming. Look for unreachable and dead code. Examine callers and called functions for side effects from the introduced changes...".

I don't think that will make much difference in a year.

reply
deleted
reply
That's not going away.
reply
Not OP, but I generally agree. Models are powerful enough now to reliably instruct other models. They don’t need fancy tools or IDEs, just the command line.

With deterministic workflows, type-safe languages and test suites, agentic loops pretty much “can’t fail”. They will continue until the types resolve, the tests pass, and the project requirements are deterministically met.

By that point it’s literally just a case of typing a prompt in to a text field, and waiting.

reply
I think I'm late to the party with cursor but I don't use it as an editor at all, I keep VS Code open on another screen for that. All I do in there is agent sessions. I would be open to something else but all the comparisons I see are out of date and talk about the IDE a lot.
reply
Same.
reply
>> Fwiw I am a c/c++ systems engineer. I think anyone mentioning anecdotal experience like this should clarify. Maybe frontend JavaScript folks have a totally different take and that's expected.

Similar experience, having transitioned from full-stack to a dedicated C/C++ stack, learned/experienced firsthand that there is no one-size-fits-all tool.

reply
I like your take and think the key takeaway is that there is no single answer for everyone. It’s like eMacs vs vim.

My one question is what popups exist in cursor? It is my daily driver and I cannot recall any popups.

reply
The code suggestions. It's highly distracting and pulls me out of my flow. I know how to code and I don't mind typing. I don't need AI making trivial suggestions. I want it to do exactly what I tell it to do.
reply
You can turn that off.
reply
I like cursor, but I'm assuming they're talking about how it hijacks your tab key. It's amazing when it works, and infuriating when I just want to insert a damn tab!
reply
You can disable that.
reply
Maybe that is it and agree.
reply
I recently made an npm package with a small C helper that runs in the background. The JS/TS code is 99.9% unit test covered and for sure "cleaner" code. Just my opinion though.
reply
deleted
reply
My experience exactly... minus c++
reply
Oh, you should try OpenSpec !
reply
On the flipside, I enjoy Cursor now and came back to it after leaving it over a year ago. The 2.5 model is fast as hell and very good. And whatever harness they have it's terrific, great results. I also really enjoy the fact that I can open my website in the Cursor in-app browser and just click and reference stuff. It's a really cracked workflow. The models can only get better for them.
reply
I would also add that Cursor's "Debug" harness is incredible. Hit "Tab" in the AI editor to Tab through the options (Plan, Multitask, Ask, etc.)

If you do any kind of on-device work, it will spin up a local HTTP log server, and pipe logs from your real device (phone, hardware, etc.) to the server and do realtime debugging.

Claude will mostly guess, have you copy + paste logs, etc.

reply
> I can open my website in the Cursor in-app browser and just click and reference stuff.

I’ve never used cursor and have only seen it in a couple work lunch and learn demos. I’ve never seen that feature. I have a lot of use cases where I’m asking cc to move a widget down a little bit or make a data table full width etc. Being able to reference the actual UI would be useful.

reply
Cursors target users are not developers but casual vibe coders.
reply