I’ve noticed a change in behavior after the latest Cursor update, and I’d like to check if there’s a way to restore the previous functionality.
Before updating, whenever the Cursor agent created or edited a file (especially when the file was not already open), the file would automatically open in a new tab in the editor. This was extremely helpful because it allowed me to visually track which files were being modified or created by Cursor’s AI.
However, after the update, this no longer happens. Files are still being edited or created correctly, but they don’t open in tabs anymore, which means I now have to manually browse through folders and files to see what has changed — making the workflow less transparent and more time-consuming.
Ideally, I’d like to restore the previous behavior: when the Cursor agent edits or creates a file, it should automatically open it in the editor tabs so I can immediately see what’s happening.
Is there a setting I can enable for this? Or is it a bug introduced in a recent update?
Thanks in advance for your help!
Best regards,
Steps to Reproduce
The way to reproduce it is: when the course is being edited or a new file is being created, tabs are not displayed like they used to be.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Without this feature Cursor is pretty much obsolete. I already told my workplace to cancel the enterprise subscription. Using claude code in regular vscode is way better now than rely on this bunge of idiots. Also just removing this without a preference to turn it back on is a break of trust they will not recover from. Multiple code bases were broken the last days because i did not realize the ais changed files in the background i did not take notice of. Cursor is completly useless now. And no, making me always click the diff button is not a solution. Its the dark ages compared to the behavior still now. I am ■■■■■■.
+1, this feature was the reason I kept using Cursor. I hope that this is a bug, if not, I’m moving to another editor, this is very annoying and breaks the workflow
+1, the alternative for me now is to manually click every changes within the chat window. I wouldn’t mind if the changed file do not open automatically due to changed initiated by background agents, but if I prompt in agent mode, I expect the changes to show up right away so that I can tweak them if needed.
@Kody_Fisher@andrewh@condor Anyone…? Anyone…? Bueller…?
Can we please get some support and answers on this UX feature?
It’s a big differentiating factor for Cursor and it clearly threatens retention with it missing.
Clearly this is polarizing, then - you find that many users think it was a nuisance, yet I see many feel it’s a critical feature. I’m in the latter group.
I get people were used to the files automatically opening up, and it should be a setting if it was something that already existed. If this doesn’t get remedied, there is a review next button to cycle through the files and a file list with the diff counts in the chat, so you can quickly navigate to the changed files (not go hunting for the file or scrolling through the chat).
The files also don’t stay open in the editor unless you start typing in them or press Ctrl+M.
I think this is much cleaner than having all the files open up after a request, especially if you were just gonna review them and click “Keep” anyways, but I can see how it would be helpful to some people’s workflows to have all the files open up in permanent tabs (sort of gets all the files open for you to start working on the task). It should still be a configurable option for people who were used to it, but for now you basically have to go through the file list or “next file” button.
Cursor should really have a beta version and a stable version that doesn’t change so much, but previous versions are here if people really need this feature.
Count me among those who relied on this feature. The automatic opening of changed files in tabs made it easy to stay in flow and quickly iterate on agent changes. Its removal has made our day-to-day use of Cursor more cumbersome, and while there were other considerations too, this change definitely contributed to our decision to end our team subscription and evaluate other tools.
