create hello world in an empty folder 
is that worth $60 a month?
1 Like
and there is no way to tell where it got stuck as far as I can see. is there a debug mode? anything?
Same issue here. Looking at earlier messages stating it is indexing problem, I tried to open IDE for a subdirectory, which helped, agent started working there. But my project is not so big now, I wonder if I will face the same issue when it grows..
hey, i’ve just fixed it by running cursor with new instance flag
open -n -a Cursor --args --user-data-dir="$HOME/.cursor-profile-2"
it opens the app with empty cursor profile (empty config) and chat works perfectly, but after running cursor with default profile again it started to work as well.
I just met the same issue, when I restart cursor, the problem has been solved.
My cursor version is already up to date.
Hopefully, the developers of cursor will fix this issue as soon as possible; it seems to be a backend problem.
If you are a VPN user (for example, living in a certain major Asian country), you can try to continue using HTTP/2.0 mode and use Proxifier to forward the traffic of cursor.app(or cursor.exe) to your vpn app.
Note that Proxifier needs to add a rule: Cursor*
still happening, feb 2026.
it is not a configuration issue, the behavior comes and goes
Can I get my money back for this issue? it keep happening
1 Like
It gets worse to the point that basic movements in the IDE get blocked…
I can’t use keyboard arrows, CMD+F for searching doesn’t work, I can’t copy/paste terminal logs.
Same problem here. Nothing is working and no solution.
same
Hi guys, I’ve had the same issue and it was very frustrating, i tried switching versions and it didnt work, but I’ve had VPN on, and turning it on/off solved the issue for me
Hello, I’ve just managed to fix the issue. For me, the issue was non-existing git worktree “vjn” where the agent was trying to start.
git worktree list
If you see something prunable here, it might be the cause
git worktree prune
I’ve also clean the cursor (running in WSL)
rm -rf ~/.cursor
rm -rf ~/.cursor-server
rm -rf ~/.local/share/cursor-agent
Restarted the WSL and cursor server and “Say hello” started to work again
Guys, it’s been 4 months since this bug was reported (November 2025), more than 14,000 people have seen it, and you still haven’t fixed it?
What does this say about your priorities…?
Hello everyone,
This thread has become a catch-all for an issue caused by many different circumstances in Cursor. A large number of these have been fixed, and we are continuing to work to reduce error rates.
As this megathread has served its purpose (and it’s simply not possible to work through individual issues in a thread this large), it would be more productive at this point to submit new Bug Reports with the complete bug template filled out.
As a result, we’re going to close this thread.
If you’re still facing the issue, please file a new bug report.
1 Like