Meet the new Cursor · Cursor

Cursor 3 is a unified workspace for building software with agents.

Cursor

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.

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.

> They've obviously had a go at being a first-party model company to address this, but that didn't work.

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