Todays version on 2022 Mac M1 chip. I have been working on Cursor with same account over a year and never experienced this. So i updated zsh path since I had an Intel related version of zsh and then I cleared any old scripts from zsh and reinstalled Homebrew. I am working on a home internet with no VPN or cloud or other placed it would get hooked. In fact from my work computer on a VPN and free account Cursor agents respond immediately. My usage is still under limit on entry Pro plan. Her is the stats and the steps that have Not worked trying to get through with Google chats. Images attached for details.
Hey @IFT, thanks for the detailed report! The troubleshooting summary actually points straight to the cause.
The “Bad CPU type in executable” you found is the key. macOS 27 no longer includes Rosetta after an upgrade, and an Intel (x86_64) git left over from your old Homebrew setup is very likely still sitting in /usr/local/bin ahead of Apple’s git. When Cursor’s agent helper tries to start that git it never gets an answer, so the Agents Window times out and the classic IDE chat hangs as soon as the agent tries to read or search a file. It is not your network or your usage limit (both look fine on our side), which is also why your work laptop is unaffected.
Can you try this:
- Open Terminal and run:
file "$(which git)" - If the output mentions
x86_64(notarm64), that is the culprit. Pick ONE of these fixes:- Reinstall Rosetta:
softwareupdate --install-rosetta --agree-to-license - Or remove the old Intel git so Apple’s git takes over:
sudo rm -f /usr/local/bin/git - Or point Cursor at Apple’s git: in Cursor Settings search for
git.pathand set it to/usr/bin/git
- Reinstall Rosetta:
- Fully quit Cursor (Cmd+Q, then check Activity Monitor for any remaining Cursor processes) and reopen it.
- While you are in settings, turn Cursor Settings > Indexing > Index Repositories for Instant Grep back on (it is not the cause, but having it off slows every request down).
- Open a new chat in Agent mode and ask it to read a file in your project.
Does the agent respond now?
It was the still hitting that x86_64. I also completed the other steps you suggested and now am hopeful there will be no more issues with Intel git. Thanks so much for your help. I can get back to my projects at last!
Hey @IFT,
Glad that got you back to your projects, and thanks for confirming!
Quick heads-up: Cursor 3.23 includes a change so an incompatible git on your PATH no longer makes the agent hang. Cursor will fall back to a working git automatically instead. Nothing you need to do since you’ve already sorted it out, but it should prevent this from happening again.