It’s great at least on Mac. If you want I dropped a review today.
https://youtu.be/AAGmJAvec9o?si=EZyijbRpBYOGwh3F
I want a rollback option. In Cursor 3.x, Ctrl + K and basic VS Code shortcuts no longer work as they used to.
Summary
PLEASE do not replace Cursor with v3.0!
The reason we use Cursor is because it’s an IDE, not because they want a Claude Code clone!
This is not about complaining about change, I’ve complained about broken changes in the past.
This is complaining about using Cursor for a specific purpose and functionality that’s seemingly being stripped out/replaced.
Forcing a layout is also really bad, not every one is using a (single) 16:9 monitor. This layout doesn’t work at all on a DualUp (16:18), and vertical ultra wide (9:21) monitors.
My Apologies, It was not clear at all I could get the Editor view back at first.
Please, don’t phase out the editor view and I’m happy 
Big fan of Cursor here, don’t get me wrong, I’m trying to use it, but can’t grasp the idea. The new screen has less functionality, and we can’t see the context consumption anymore.
Also, the one thing I was expecting in an agentic window was the ability to see multiple agents running side by side, which is still not possible. It feels like you guys want to make it more “Vibe Coding", but compared to using Claude Code, what I want is to orchestrate multiple agents in parallel, have a clear view of how they are working and be able to work on files when needed with full control.
How could I get old review UI in Cursor 3? The current UI doesn’t show the last iteration change, it show total Git changs! The previous UI was so helpful! Also, the code were highlighted in a prominent way, now I struggle to see what’s new and what’s old with that narrow bars on the left. I have slight color blindness. Make them thicker maybe?
And return the per-iteration diff, that was a HUGE feature that I really miss.
I had to roll-back to 2.3 to achieve the desired behavior 
Is this using a separate backend than VS Code?
The reason I’m asking is that for our workflow it feels like a significant downgrade:
- Doesn’t support our multi-folder workspace correctly
- We have LSP plugins that are not currently loaded in that view, so the exploration of the code is very very limited because we can’t jump from the symbols to definitions and usage
- Same with other utility plugins like translations tools like i18n-ally or formatting with Prettier
- Themes and other vs code settings seem to be ignored
We use Cursor 2 agent mode a lot (and I’m glad to see it’s still there). Cursor’s compatibility with VS Code plugins was always its competitive edge over other tools for us. Are you planning to bring back that inter-operability or are you looking to get away from it in favour of your own marketplace? Hopefully it’s not the latter.
I do like to split my screen with 2 cursors, and simultaneously monitor / fire off tasks.
The new Interface is forcing me to keep the conversations panel open which would be then duplicated across my duel windows.
And therefore I prefer the Editor view… unless you can deal with this.
The AI first UI is good for laptop screens but if Im on my full 3x 27 inch screen setup, I need to split windows to have less clicks when changing.
Yes, it looks like that, because I couldn’t find VSCode menu items.
NOW WHAT WE ASKED FOR?? please focus on IDE this new UI is not useful, it’s basically loveable or codex
So basically you guys dropped a vibe coding interface, practically nothing that a real developer can benefit from. Great.
This new UI is completely un-usable if you want to any kind of human in the loop development. I just tried it out on something that is extremely trivial to do in the old UI:
- vibe code on some changes
- make a few manual tweaks…. this is where it all falls apart and the decision to drop VS Code just makes zero sense.
When making manual changes to code:
- No highlights of what has changed (no diff)
- No VS Code extensions
- No auto formatting e.g. prettier so my ci checks will fail
- No theming
If this is the direction for cursor I am extremely concerned, building on top of VS Code is what made the adoption so seamless, not building the Agent UI on top of this developer focused foundation seems like such a mistake.
I enjoy using cursor and of course I gave a try to test cursor 3.0. However I’m completly blind now. As developers we need more control. is it due so many bugs, or bad design choices.
My question is, are you going to move on from VSC to own agent windows? Are there any plans to continue development, patching etc for our loved VSC based cursor?
Hey, Cursor team, any plan or timeline for wsl2 support for the new Agents window?
I know the general sentiment for this update is negative, but I actually like it.
It takes quite some getting used to and is definitely a different way of working if you come from hands-on SE. Source code is no longer the center of attention, and the massive chat window is (honestly) wasted space. Lots of bugs and missing QoL features we love in VSCode. Still the core pieces move in the right direction: A better diff viewer, ease of starting/monitoring cloud agents, giving the integrated browser more space.
I think it will fit you if your codebase happens to be at a level where you primarily review output and orchestrate agents. Otherwise you will suffer and be better of with an agentic IDE, instead of something that is starting to look like an integrated workflow orchestration tool.
Can I only have a maximum of 3 workspace? Each time I open a workspace it only lets me have up to 3.
Fantastic update, I love it, thank you guys.
Thanks for the feedback, can you give an example of a pain point that made you want to switch back?
You can only have 1 Agents window open at a time, but you shouldn’t be limited in the number of workspaces you can work with.
It’s in progress - as in, extremely far along. Expect updates soon. Thank you for your patience!