Some commands work, some not. No idea why:
This is exactly what itās doing to me! it makes it not even usable. Itās cost me almost a week of my project.
Iām curious if anyone from Cursor devs is following this thread. Looks like itās quite annoying issue for multiple people out there. And I wonder how many arenāt just reporting.
Same issue here, really slowing me down
This issue also affected me for the past 2 weeks, up until today when now itās more severe: the tool shows no output at all. Clean reinstall, tried multiple shells. I have no workaround so far.
When I am using claude sonnet 3.7 max, it does not happen. Why different exist ?
Im facing the same issue
Popping the terminal gets the agent going again, but it frequently canāt see the results, so it tries the command again (or worse, āa different approachā) and then gets stuck in the same place. SO FRUSTRATING.
I have shell integration enabled and still get this issue. Iām using remote WSL. The issue I have is that it works fine⦠sometimes. And then it starts hanging and hangs most of the time.
+1 exactly as described
Please, Cursor team, take a look at this. I can help reproduce or w.e., DM me if needed. This is really a blocking bug in a lot of ways. @danperks
+1 exactly as described
Experiencing the same issue. yolo mode worked for me when first starting to use cursor a couple weeks ago, now itās broken as described.
This is not a fix
Hey there! Yash from the Cursor team here. I am looking into fixing this issue now. Would love to hear from yāall if there are consistent steps you use to reproduce this broken state.
exactly the same issue here.
Env:
Version: 0.48.6 (user setup)
VSCode Version: 1.96.2
Commit: 1649e229afdef8fd1d18ea173f063563f1e722e0
Date: 2025-03-31T05:21:50.407Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19044
Tried solution above but did not help.
I am connect via SSH and simplely ask agent to execute ls.
I could see the command executed and result on ternimal.
the terminal could work after command.
I could input more command in the same terminal with correct result.
Agent is waiting for the result somehow.
I do not know if itās related.
If I run ācd PATH && make clean && make &&./mainā, i failed
If ask agent to run command one by one, itās likely okayā¦
agree, its not fixed - happe 0.48.6 with long terminal output for me
It looks like its related to the output of a different commands. If the output uses less it will freeze. In my case, Iām bypassing this issue by piping the commands to cat. So something like: Use git diff --staged | cat
makes it work for me.
How do you see the log that sheds the light on how the tools are called, terminal tool specifically? Iām seeing so much ātool call timeoutā and stuck terminals, Iām inches away from switching to another IDE at this point.
As for ways to replicate, it for sure happens all the time on my Ubuntu machine when I use it via SSH. Consistently around 5 times in an hour, but in some chats it happens once and then repeats forever. Can only tell this much without any transparency in the tool calling process.
Please consider making this more transparent in the UI, less āmagicalā, at least give an option. I would happily tweak something if I can figure out myself at least how not to trigger bugs like these.