I am a heavy Cursor user and am currently using Cursor to develop an indie app. I use two $200-per-month plans every month. The recent 3.0 update has caused me significant trouble. First, I cannot rename agent windows, and when running a large number of tasks in parallel, I really need to follow a clear naming convention for each agent. Second, the stability of sub-tasks has dropped significantly. On the day of the April 9 update, I kept trying to restart, reinstall, and reopen conversations. Cursor is now completely unable to handle larger conversations; it constantly freezes and swallows sub-tasks without any indication. I’d like to configure it so that sub-task content remains visible in the main window rather than in the agent’s view. The current version makes it impossible for me to work. Please fix this as soon as possible.
Steps to Reproduce
I’m not sure why, but this has been happening consistently for me. I’ve tried it on two different computers, and the issue persists on both. I also tried rolling back to version 2.6, but that didn’t resolve the problem. Furthermore, conversation caches between versions 2.6 and 3.0 are not compatible; rolling back from 3.0 to 2.6 causes all session caches to be lost. I need to recover my tasks now.
Renaming agents – this IS available in the new Agents Window. You can rename agents by double-clicking the agent name in the sidebar, or by right-clicking the agent and selecting Rename from the context menu. The interaction changed from the old tab-based approach, so it’s easy to miss.
Sub-task (subagent) stability – this is a known issue our team is aware of. Subagents can sometimes get stuck or silently fail, particularly during heavy parallel usage. The team is actively working on improving subagent reliability.
Freezing with larger conversations – since you mention this happens on both version 2.6 and 3.0, and on two different computers, it may be related to accumulated session data rather than the version itself. Could you check the size of your state database file? On Windows, it’s at:
%APPDATA%\Cursor\User\globalStorage\state.vscdb
If this file is over 1-2 GB, it can cause performance issues and freezing. Deleting it (with Cursor closed) will reset the conversation history, but should fix the freezing.
Also, could you open Help > Toggle Developer Tools and check the Console tab for any red error messages when the freeze happens? That would help narrow down the cause.
Session cache between versions – unfortunately, conversation data from 3.0 is not compatible with 2.6 due to architectural changes. There is no migration path between the two formats, so rolling back will result in the loss of 3.0 conversations. We understand this is painful, especially for an active workflow.
For the sub-task visibility preference (keeping sub-task content in the main window), I’d suggest posting that as a separate feature request so the team can track it.