Agent Bug -- Chats not sending

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: 84e0ede1-afb0-47a5-9fc5-a0d492d84210 {“error”:“ERROR_EXTENSION_HOST_TIMEOUT”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.”,“isRetryable”:false,“shouldShowImmediateError”:true,“additionalInfo”:{},“buttons”:[{“label”:“Reload Window”,“reloadWindow”:{}}],“planChoices”:}} The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Agent Execution Timed Out [deadline_exceeded] ConnectError: [deadline_exceeded] Agent Execution Timed Out at vum (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8866:39609) at Hvi.waitForProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8866:45097) at async KJl._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:20833:3630) at async lWe (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:7526:11655) at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:20833:10618 at async lWe (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:7526:11655) at async KJl.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:20833:10515) at async KJl.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:20833:38905) at async fHe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8848:4456) at async fHe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8843:67470)

Steps to Reproduce

I just tried sending a chat message on agent. I did update to ios27 on mac so it may have something to do with that?

Expected Behavior

works

Operating System

MacOS

Version Information

Version: 3.21.16
VS Code Extension API: 1.128.0
Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000
Date: 2026-09-19T06:43:22.276Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi @Clement_Decrop thanks for the report, and yes, the macOS 27 update is the trigger.

macOS 27 does not carry Rosetta over when you upgrade. If an Intel-only git is first on your PATH (usually an older Homebrew install in /usr/local/bin), Cursor’s agent helper waits on it forever and the Agent window times out. That also explains why your Gmail, Google Calendar and Google Drive plugins could not update this morning; they use the same git.

Can you try this?

  1. Quit Cursor completely (Cmd+Q).
  2. Open Terminal and run: file “$(which git)”
  3. If the output says x86_64 and not arm64, do ONE of these:
    a. Reinstall Rosetta: softwareupdate --install-rosetta --agree-to-license
    b. Or remove the old Intel git so Apple’s built-in one is used: sudo rm -f /usr/local/bin/git
    c. Or keep it but point Cursor at Apple’s git: Cmd+Shift+P, “Preferences: Open User Settings (JSON)”, add “git.path”: “/usr/bin/git”
  4. Reopen Cursor and send a short prompt in the Agent window, for example “list the files in this project”.

Does the agent respond after step 4? Please paste the output of step 2 either way. If it already says arm64, also run file “$(which node)” “$(which ssh)” and paste that too, and we will dig further.

12

Hey @Clement_Decrop,

Quick update: we’ve landed a fix so the Agent no longer hangs and times out when an older Intel-only git is first on your PATH after the macOS 27 upgrade. It will be included in an upcoming version of Cursor.

If the Rosetta or git steps above already got the Agent working again, you’re all set and don’t need to change anything.

Otherwise, once the new version reaches you, give it another try and let me know if you still hit it.