Composer multiple tool issues

Bug Report
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

  1. The most annoying issue is the composer has a habit of canceling the tool run (see screenshot)
  2. The composer tool run will work some rounds (1 or 2), and by the 2nd or 3rd time it will freeze on loading (which I have a temp solution)

Steps to Reproduce

  1. Random in general, I have noticed the composer will determine when to cancel and then retrieve the output (even for a tool run without this issue), just when the session gets longer and longer (20+ rounds), it will get worse and worse
  2. Happens when a session invokes 3+ tool runs, by the 2nd or 3rd time, it will be trying to hook with the previous terminal instance but seems to fail. My temporary solution is to pop out and remove the terminal every time the composer completes the last tool run (and retrieved the output)

Screenshots / Screen Recordings

Screenshot 2025-01-07 205240.png
Screenshot 2025-01-07 205240.png813×582 21.7 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

Additional Information

I have mutilple Windows PC having these problems, and they were there since 0.44.8

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

image
image934×594 25.6 KB

lol now I have to “tell” the model that we have a team member that will interrupt the tool run randomly, and need the composer to try rerun until it got the result…

and even the composer itself will have a small celebration when it can retrieve the actual output

3

This is a weird one, as I’m not sure what’s going on here but I’ve reported this to the team to look into!