Agent execution timeout error in Cursor

Support Bug Reports
1

Same. I have had this same problem for a few days now. Tried downgrading but no luck. Any version of cursor has same problem. Request ID: fe281508-a749-4e26-9ac7-66cf98223739
{“error”:“ERROR_CUSTOM”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond within 16 seconds. This may indicate the extension host is not running or is unresponsive.”,“isRetryable”:false,“shouldShowImmediateError”:true,“additionalInfo”:{},“buttons”:[{“label”:“Reload Window”,“reloadWindow”:{}}],“planChoices”:}}
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11441:8322
at async BWf.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11441:6375)
at async NMg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:529:551502)
at async CW.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9097:16084)
at async D1a.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11441:1272)
at async ilb.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34249:14278)
at async ggc.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34259:3575)
at async ggc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34259:5180)
at async ggc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34259:8576)
at async qTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9180:14965)
at async Xi (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:33004:3808)

2

Oh and yes, it uses tokens but the client seems disconnected

3

Hey, this is a known issue. The team is aware and tracking it.

For now, try a few things:

  1. Clear the workspace state (this helps most often):

    • Fully close Cursor
    • Delete or rename this file: ~/Library/Application Support/Cursor/User/globalStorage/state.vscdb
    • Start Cursor again (you’ll need to log in again)

  2. Start without extensions to rule out an extension conflict:

    • In Terminal: cursor --disable-extensions
    • If it works, turn extensions back on one by one to find the one causing it

  3. Do a full reinstall

    • This can help if old files are left behind after updates

Here’s a thread with a similar issue and more context: Agent timeout within 16 seconds

Let me know if any of this helps.

4

Hi, the option 1 seems to delete chat history?

5

Yes, deleting state.vscdb can reset your chat history since that file stores workspace state, including session data.

If you want to keep your history, try less destructive options first:

  • Cmd+Shift+P then Developer: Reload Window
  • Start Cursor without extensions by running cursor --disable-extensions in your terminal
  • Fully quit and reopen Cursor

If none of that helps and the timeout is still there, then deleting state.vscdb is the last resort. Before you delete it, you can export any important chats.

Also, what version of Cursor and what OS are you on? This error often depends on the exact setup.