Cursor agent execution timeout (“deadline_exceeded”) on v3.4.20 MACBOOK

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Cursor AI agent fails to execute requests and times out with “deadline_exceeded” or “agent execution provider did not respond in time.” The IDE reports that the extension host may be unresponsive, causing chat/composer/agent features to stop working even though the application and internet connection are otherwise functioning normally.

Steps to Reproduce

Open Cursor on macOS (v3.4.20) and attempt to use Chat or Composer in any workspace. The AI agent fails to start execution and times out after a short period. The IDE shows errors such as “agent execution provider did not respond in time” or “deadline_exceeded,” and may indicate that the extension host is unresponsive. The issue can be triggered consistently after launching the app and attempting the first AI request in a session.

Expected Behavior

The AI agent is expected to start the extension host process, send the request to the backend, and return a response in the chat/composer. Instead, the extension host does not respond or becomes unresponsive, causing the agent execution to time out before any response is returned. As a result, Chat/Composer/Agent features fail to run even though the IDE itself is open and functioning normally.

Screenshots / Screen Recordings

Screenshot 2026-05-20 at 14.56.59.png
Screenshot 2026-05-20 at 14.56.59.png2928×1642 187 KB

Operating System

MacOS

Version Information

Version: 3.4.20 (Universal)
VSCode Version: 1.105.1
Commit: 0cf8b06883f54e26bb4f0fb8647c9500ccb43310
Date: 2026-05-15T02:26:10.351Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

For AI issues: which model did you use?

On all models incl. Auto and Premium.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report. This looks like a known pattern on the Glass layout. If the workspace isn’t trusted, cursor-agent-exec won’t activate and you’ll only see a timeout with no trust prompt. The GOEDETEMP folder looks newly created, which matches this scenario. On Glass, the Manage Workspace Trust item also doesn’t show up in the Command Palette, which is part of the same issue.

Workaround:

  • Open an Editor Window with Cmd+Shift+N or use the Editor Window ↗ button in the top-right corner.
  • Open VS Code settings with Cmd+Shift+,
  • Search for security.workspace.trust.enabled and uncheck it.
  • Run Cmd+Shift+P then Developer: Reload Window.

We’re tracking this on our side, but I can’t share an ETA for a fix yet. Let me know if the workaround helped.

8

Hey @Sufyan_Zeroual quick update on this bug. The fix for the Glass agent-execution timeout on untrusted workspaces is included in Cursor 3.7. It’s not in the current stable version 3.6.31 yet, so please try again once you’ve updated to 3.7.

Until then, the workaround from the post above still applies. Turn off security.workspace.trust.enabled via the Editor Window, then do Reload Window. Let me know if the issue still happens after you update.