Cursor v0.44.10: Composer Agent Mode Unresponsive After Extended Use

Bug Reports
1

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

Cursor Composer intermittently becomes unresponsive after an extended session with a large number of messages, particularly when using Agent Mode. Agent Mode also feels generally slower compared to previous versions, with more frequent periods of apparent processing that might be related to how much context the mode is using (but this is speculative). When the unresponsiveness occurs, the composer enters a perpetual loading state and fails to generate a reply. Eventually, after a prolonged period of loading, Composer displays a “Connection Failed” error message, even though the internet connection is stable and other applications are working fine.

Steps to Reproduce

The issue has not been consistently reproduced. However, it typically occurs after:

  1. A prolonged session in Cursor Composer, especially in Agent Mode.
  2. Sending a large number of messages (exact threshold unknown).
  3. Attempting to generate a new response after the extended session.

Expected Behavior

Composer should ideally continue to generate responses, even after a large number of messages, in both Normal and Agent Modes. If a connection issue genuinely occurs, the error message should be accurate and helpful.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.44.10
VSCode Version: 1.93.1
Commit: ae296fde8115b123d8ce516cdfedf697fc577660

Additional Information

  • The problem started occurring in version 0.44.X and was not present in version 0.43.6, where Agent Mode was notably more stable, albeit with fewer features.
  • Switching between using Cursor’s provided Sonnet access and a custom Anthropic API key for the Sonnet model does not resolve the issue.
  • The issue occurs approximately once every two days during prolonged usage and is significantly worse in Agent Mode. Normal Mode does not appear to exhibit the same progressive slowdown.
  • A workaround exists where I can go back many messages, request a summary, and use that to start a new Composer instance. However, the original instance remains unusable.
  • I initially delayed reporting this issue after updating to 0.44.3, assuming a fix was in progress.
  • While this issue does not stop me from using Cursor, it is a significant inconvenience, especially during long sessions.
  • Given the severity of this issue and its impact on my workflow, I would strongly prefer a minimal, stable mode for Agent Mode as an interim solution. This could be a setting to turn off certain features, or it could be a separate mode altogether. A stable experience, even with reduced functionality, is highly preferable to the current unreliable behavior. The “minimal mode” should prioritize stability and responsiveness, potentially resembling the more reliable Agent Mode in version 0.43.6.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor