2.0 has lost a lot of functionality I can no longer use Cursor.
2.0 removed a large number of features, and the Agent Window shifted the familiar Workbench to the right, so Iâve decided to go back to Copilot.
10 Likes
Are there any screenshots?
The /init command for automatically generating the initial rule file is also goneďźWhat is the alternative solution?
Itâs early access, so things might not yet be polished.
Just reinstall 1.7.54: https://downloadcursor.app
1 Like
@E_T Check "/Generate Cursor Rules" Custom Command Workaround! if you still need this functionality
I donât think soâaside from the UI/UX (with the mandatory Primary Side Bar on the Right), their 2.0 version simply removed their original, flawed design. Yet, they didnât offer any migration plan for existing users, making it a truly terrible product.
Here: CRITICAL: Cursor 2.0 - no "Past Chats" and specific Git commits as the context types? - #5 by danperks, they say itâs because past functionality was unreliable or wasnât working at all.
I agree, this is strange. If it wasnât working, why wouldnât you fix it? The proposed workarounds are strictly more monkey work for the user. Or at least communicate these feature removalsâŚ
2 Likes
The Cursor team often adopts a strategy where, if they canât fix a bug in a particular feature, they simply remove that feature altogetherâmuch like the logic behind Claude Sonnet. This approach ultimately determines how far their product can go, despite having already secured a first-mover advantage.
4 Likes
The current changes in version 2.0 have made Cursor and other tools virtually indistinguishable, leaving them completely unable to compete on differentiation. Iâd be happy to give other tools a try instead.
The new Agent Windows in version 2.0 now forcibly places the Primary Side Bar on the right, completely eliminating any possibility for me to experiment further. Goodbye, Cursor.
5 Likes
https://downloadcursor.app â and what would guarantee that this silly url isnt offering a serving of malware on the side?
Cursor really need to offer an easy, secure and accessible way to let users downgrade and upgrade without relying on random 3rd parties or external urls.
4 Likes
The official release offers multiple versions, but this isnât a matter of downgradingâitâs about determining what the future product will look like. If you know the current version wonât suffice, switch promptly to the product you actually want, rather than resorting to downgrading as a workaround.
2 Likes
A fair question. GitHub source is available here for inspection:
(The silly app includes this link at the bottom)
All downloads link directly to Cursor servers.
1 Like
This isnât the main point of the discussionâitâs completely irrelevant.
1 Like
Is it possible that you can no longer add error messages from the terminal as context to the chat, or is this problem only occurring for me?
I have been very concerned this was going to be how Cursor resolved all of their broken context tools. They broke them over a month ago, and they seem to be giving the issues no attention. They are just plowing forward with new features and now an entirely new major version. I do not appreciate how Cursor is decimating their featureset just to keep moving forward. I cannot use their new terminal sandbox, its a disaster, I heavily rely on the allowlist, but they seem determined to eliminate the allowlist and force us all into using their sandbox mode. This is a non-starter or me. I had been a heavy user of @Docs in the past, but that hasnât worked for months now. I was a heavy user of @Prior Chats and @Active Tabs, but those donât seem to work. Etc. etc.
The Cursor team had a months-long devastating issue with Terminals, and their fix has resolved some issues, but left others in their place.
I donât know what the Cursor team is doing, but they are destroying their product. If they remove all these features in v2, I donât know what will be keeping me tied to Cursor anymore⌠This was a great product six months ago. Today its an absolute mess of who knows whatâs gonna get axed nextâŚ
Extremely frustrating. I canât work without the allowlist for terminals. I WILL NOT use their sandbox, I donât trust it and it is simply not viable for my use cases, but the alternative of having to manually allow every single command including totally benign ones is ludicrous.
Iâm very rapidly going from really liking Cursor to absolutely hating it, and I donât even think the Cursor team has a coherent plan to keep their users, who rely heavily on the features they ONCE HAD, supported. If this is a glimpse of the future with Cursor â2.0â (why they are going to 2.0, I honestly cannot fathom, not with the breadth and depth of issues they currently have), total decimation of featureset, then Iâm probably outâŚ
13 Likes
this last update really crashed everything, I will try to install 1.6 again
3 Likes
I can relate with lots of the issues you mentioned and feel the same.
Cursor just breaking the allowlist system for sandboxed and non-sandboxed agents is one of the worst product upgrade experiences Iâve ever been forced to witness. Even worse that itâs in a product that I love and depend on.
Assuming you are seeing the exact same issue as I was, the problem comes from old Yolo/security garbage settings you may have saved in the past, which cursor somehow still listens to but doesnt bother showing in the UI 
If thatâs the case you might actually find a solution in a script i wrote (ok, actually codex wrote it but I was cheerleading the whole time!)
5 Likes
In my case, the allowlist is for terminal commands. I use MCP, but lately I havenât been as much. Did they nuke allowlist for MCP AS WELL??
The Cursor team is actively nuking themselves right now. I donât know what they are doing, but they are totally off the rails now. You canât butcher heavily used features and replace them with things that are not viable drop-in replacements overnight. This is getting absolutely ludicrous.
We are not a bunch of social media throngs who donât care about anything but likes. We are professionals who need powerful, feature-rich tools with STABLE feature sets to get our jobs done every day. Since 1.5, Cursor has just been eating themselves alive. I really hope they pay attention to their users here, because if they continue on this track, they are going to lose most of them.
I cannot use Cursor with their sandbox, its a joke. I cannot be required to approve every single little terminal command (or MCP command, for that matter) that the agent decides to execute, ESPECIALLY if they are KNOWN BENIGN commands. Removal of the allowlist is the worst decision they have made recently, and it will likely force me to look at alternatives. I am far too heavy a terminal user to be stuck manually approving every command (I WILL NOT, EVER, allow the agent to execute every and any command it wishes without restriction, ever.) Sandbox is read-only as well, which does not meet my needs as many of the commands I need to be executed will WRITE.
Really ticked off right now, at the way Cursor is being managed. This is NOT conducive to a userbase of PROFESSIONALS. Decimation of feature sets that their users rely on is only going to â â â â people off. Case in point right here.
6 Likes