I just switched to a new Mac (went from Intel 2020 mac to M5) and reinstalled Cursor for the M distribution. If I’m in an ssh or a local repo, I am getting the following issue:
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.
I’ve tried hard refreshing as well as switching models. My git version is slightly deprecated but I don’t know if that’s the issue. Is this a known issue with new computers?
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive
I have read threads on the forum and have tried some of the fixes but nothing has seemed to work so far. Any support would be amazing!
Apple M5 Macbook
Steps to Reproduce
Open Cursor
Generate any request in ask, code, etc. mode
wait
Expected Behavior
Cursor’s amazing functionality!
Operating System
MacOS
Version Information
3.17.21 IDE
For AI issues: which model did you use?
All
For AI issues: add Request ID with privacy disabled
Hey, thanks for the detailed report. This error means the Cursor component that starts agent requests didn’t start on your machine, so requests time out before they ever reach our servers. It’s not related to your account, models, or settings, and it matches well with moving to a new Mac.
Try these in order:
New Apple Silicon Macs don’t come with Rosetta by default, so anything Migration Assistant brought over from an old Intel Mac old git, Intel Homebrew tools, etc might not run. You mentioned your git is a bit outdated, and an Intel-only git is a known trigger for this error. Run softwareupdate --install-rosetta in Terminal, or better install a current native git via xcode-select --install, then restart Cursor.
If the app itself or its data was copied instead of installed fresh, run xattr -cr /Applications/Cursor.app in Terminal and restart.
Try temporarily disabling migrated extensions. Quit Cursor, rename ~/.cursor/extensions to ~/.cursor/extensions-old, then launch Cursor again. Extensions migrated from an Intel Mac can also block this component from starting.
If the issue still happens, open the Command Palette with Cmd+Shift+P, run “Developer: Show Logs”, select “Extension Host”, and paste what shows up around the time the error appears. That log usually shows the exact reason the component didn’t start.