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.
It's a very tough spot they're in. They have a great product in the code-first philosophy, but it may 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.
I thought there was an entire initiative to build their own coding model and the fine tunes of in Composer 1.5 and Composer 2 were just buying them time and training data
I thought it was primarily a user of Anthropic and OpenAI APIs, so the fewer tokens you use to accomplish a task, the higher their margin.
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.
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.
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 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).
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.
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.
I get the temptation of letting agents do everything. But they create really bad systems still (bad architecture, reimplementation of solved problems etc).
I also get the temptation for beginners and think it’s great that more people are empowered to build software but moving entirely to chat means they won’t learn and level up which in the long run limits their ability.
I could be wrong. And my way of thinking is dying but thankfully I can build the tool I want.
Still curious which ones will survive when the AI gold diggers finally settle.
I haven't used it in a decade, Im sure it has has evolved
Can’t say I miss eclipse, but a lot of the VSCode extensions seems to utilize old legacy eclipse stuff and has the bugs to match.
If not you really should. IntelliJ with Java is one of the best dev experiences I've ever had. I'm a VSCode fan for most other things but for Java I wouldn't even remotely consider using it over IntelliJ if I had the option :-)
2. Cursor's UI allows you to edit files, and even have the good old auto-complete when editing code.
3. Cursor's VSCode-based IDE is still around! I still love using it daily.
4. Cursor also has a CLI.
5. Perhaps more importantly, Cursor has a Cloud platform product with automations, extremely long-lived agents and lots of other features to dispatch agents to work on different things at the same time.
Disclaimer: I'm a product engineer at Cursor!
And I would happily pay a seat based subscription fee or usage fees for cloud agents etc on top of this
Unfortunately very locked into these heavily subsidized subscription plans right now but I think from a product design and vision standpoint you guys are doing the best work in this space right now
Cursor is an IDE and an agentic interface and a cli tool and a platform that all work locally and and in the cloud and in the browser and supports dozens of different models.
I don't know how to use the thing anymore, or what the thing actually is.
I applaud Cursor for experimenting with design, and seeing if there are better ways of collaborating with agents using a different type of workspace. But at the moment, it's hard to even justify the time spent kicking the tires on something new, closed source and paid.
For $20 a month, I can plan and implement thousands of features using Composer 2 or Auto with Cursor. The usage limits are insanely higher. Yes, the depth of understanding is not Opus 4.6, but most work doesn't need that. And the work that does need it I pass to Claude.
I can code 8 hours a day using LLMs as my primary driver spending just $40 a month.
I am not saying this in bad faith. Model companies cannot penetrate every niche with the same brand recognition as some other companies you would consider as "API resellers" do.
Every company I've worked at has still had a few engineers who insist on working exclusively in the CLI with vim/emacs prior to AI. Every other engineer used some flavor of a desktop app ranging from more minimal editors to incredibly complex IDEs. I expect we land back on UIs long term.
These are features I am sure Codex will soon have, of course.
Then there is the advantage of multiple models: run a top level agent with an expensive model, that then kicks of other models that are less expensive - you can do this in Claude Code already (I believe), but obviously here you are limited to something like Haiku.
One of my favorite startups and I genuinely like to keep subscribing to them.
I think it's a really solid release, and while cursor seems to have fallen out of the "cool kids club" in the past three months it remains the most practical tool for me doing AI-first work in a large production code base. The new UI works better in a world where agents are doing most of the work and I can hop back into the IDE interface to make changes.
We've set up a linear integration where I can delegate simpler tasks to cloud agents, and the ability to pick that work up in cursor if I need to go back in forth is a real productivity boost. The tighter integration with cloud agents is something I've been hoping for recently.
I appreciate not being tied at the hip to one model provider, and have never loved doing most of my work from the command line. I was on vs code + meta's internal fork of it for years prior to the current AI wave, so that was a pretty natural transition. I'm pretty optimistic on cursor's ability to win in the enterprise space, and think we're going to see open source models + dev tools win with indie devs over things like claude code as costs start getting passed down more and the gap between frontier models and open source gets tighter.
What's the pitch for using Cursor now a days?