adamfeldmanCursor 3
Man, I wish they'd keep the old philosophy of letting the developer drive and the agent assist.
I feel like this design direction is leaning more towards a chat interface as a first class citizen and the code itself as a secondary concern.
I really don't like that.
Even when I'm using AI agents to write code, I still find myself spending most of my time reading and reasoning about code. Showing me little snippets of my repo in a chat window and changes made by the agent in a PR type visual does not help with this. If anything, it makes it more confusing to keep the context of the code in my head.
It's why I use Cursor over Claude Code, I still want to _code_ not just vibe my way through tickets.
Agreed completely on this (as a heavy daily user of Cursor). It's been the perfect in-between of coding by hand (never again!) and strictly "vibe coding" for me. Being able to keep my eyes on all the changes in a "traditional" IDE view helps me maintain a mental model of how my systems work.
I'm hoping in this new UI in v3 I can still get that experience (maybe it's just hidden behind a toggle somewhere for power users / not shown off in the marketing materials).
I'm an engineer at Cursor, can try to clarify questions here.
> I wish they'd keep the old philosophy of letting the developer drive and the agent assist. Even when I'm using AI agents to write code, I still find myself spending most of my time reading and reasoning about code.
We very much still believe this, which is why even in this new interface, you can still view/edit files, do remote SSH, go to definition and use LSPs, etc. It's hard to drive and ship real changes without those things in our opinion, even as agents continue to get better at writing code.
> I'm hoping in this new UI in v3 I can still get that experience (maybe it's just hidden behind a toggle somewhere for power users / not shown off in the marketing materials).
This new interface is a separate window, so if you prefer the Cursor 2 style, that continues to exist (and is also getting better).
> We very much still believe this
That's good to hear, I might have jumped a little too quickly in my opinion. It's a bit of a Pavlovian response at this point seeing a product I very much love embrace a giant chat window as a UX redesign haha.
I would love to see more features on the roadmap that are more aligned with users like us that really embrace the Cursor 2 style with the code itself being the focal point. I'm sure there's a lot you can do there to help preserve code mental models when working with agents that don't hide the code behind a chat interface.
Once I downloaded it, it made sense. The blog post almost made me cancel my subscription because it seemed to get rid of the IDE entirely.
> It's been the perfect in-between of coding by hand (never again!) and strictly "vibe coding" for me.
I dont think there is an inbetween. Its really hard to 'keep an eye' on code by casually reading diffs. Eventually it will become vibe coding.
Software engineers are deluding themselves with spec driven, plans, prds whatever nonsense and thinking its not vibecoding.
AI labs think they’re building an autonomous replacement for software engineers, while software engineers see these systems as tools to supplement the process of software engineering.
Yeah that's the disconnect though right? Even with the best frontier models, you need to do a lot of system design work, planning, and reviewing before you can let these models run.
These models are infinitely more effective when piloted by a seasoned software engineer and that will always be the case so long as these models require some level of prompting to function.
Better prompts come from more knowledgeable users, and I don't think we can just make a better model to change that.
The idea we're going to completely replace software engineers with agents has always been delusional, so anchoring their roadmap to that future just seems silly from a product design perspective.
It's just frustrating Cursor had a good attitude towards AI coding agents then is seemingly abandoning that for what's likely a play to appease investors who are drunk on AI psychosis.
Edit: This comment might have come off more callous than I intended. I just really love Cursor as a product and don't want to see it get eaten by the "AI is going to replace everything!" crowd.
> AI labs think they’re building an autonomous replacement for software engineers
And management everywhere is convinced that thats what they are paying for. My company is replacing job titles with "builder". Apparently these tools will make builder out of paper pushers hiding in corporate beaurcarcy. I am suddenly same as them now per my company managment.
How would they make money from the tokens then haha? The main revenue driver of these companies is to get people to use more tokens. That’s what they will optimise for. Getting the developers out of the way is the way to do it.
Isn’t Cursor’s business model mostly subscriptions? They’re the ones paying for inference, not the user directly, right? So wouldn’t they be incentivized to minimize token usage per unit of user value, not maximize raw tokens?
It's pay-as-you-go after a certain number of included requests/tokens: https://cursor.com/docs/models-and-pricing
My guess would be this is less driven by product philosophy, more driven by trying to maximise chances of a return on a very large amount of funding in an incredibly tough market up against formidable, absurdly well-funded competitors.
It's a very tough spot they're in. They have a great product in the code-first philosophy, but it may just turn out it's too small a market where the margins will just be competed away to zero by open source, leaving only opportunity for the first-party model companies essentially.
They've obviously had a go at being a first-party model company to address this, but that didn't work.
I think the next best chance they see is going in the vibe-first direction and trying to claim a segment of that market, which they're obviously betting could be significantly bigger. It's faster changing and (a bit) newer and so the scope of opportunity is more unknown. There's maybe more chances to carve out success there, though honestly I think the likeliest outcome is it just ends up the same way.
Since the beginning people have been saying that Cursor only had a certain window of time to capitalise on. While everyone was scrambling to figure out how to build tools to take advantage of AI in coding, they were one of the fastest and best and made a superb product that has been hugely influential. But this might be what it looks like to see that window starting to close for them.