Why would the Cursor team would just up and remove the Cloud option from the IDE’s New Agent dropdown? It became a part of my preferred workflow, I updated to the new IDE, and suddenly it’s gone, without even a hint at where to find the moved functionality. (At least the Worktree disabled option hints that “worktree” is now a / command.) Meanwhile, the changelog gives a one sentence nod to doing so, without any reason or justification.
Hi @MishaTheMisha Thanks for the feedback! With Cursor 3.0, we moved cloud agents into the new Agents Window (which you can access with Cmd+Shift+P → “New Agents Window”) or simply File → New Agents Window. Cursor 3.0 comes with lots of features and a brand new, future-oriented UI, and it made sense to focus our resources on delivering an excellent user experience in one place in the Agents Window rather than splitting it across multiple surfaces.
This seems like a major regression in user experience at the moment. There isn’t a good way to browse code and inject it into a prompt to a cloud agent in either the “Editor Window”, the “Agents Window” or the cursor web interface.
I understand the emphasis on the capabilities of the new Agents Window, and reducing the splitting of Cursor’s resources on the “old” version of the product, but this strikes me as really poor versioning/change management for users who have become dependent on the software (and who strongly proselytize for its use among their tech team).
Again, even just a tooltip on a disabled select option would’ve reduced the friction of logging onto a newly updated version and my core workflow being broken without warning.
