Agent Error Timeout and skills, rules or commands not loading

[mirocon (Miro)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Can’t process any request and skills are not loading, usage is marked as 0%

Steps to Reproduce

Made request to agent and is not responding, tried with different models

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Cursor IDE

For AI issues: which model did you use?

Any model

For AI issues: add Request ID with privacy disabled

Request ID: 443785b0-194d-43e7-9265-187edfffb761
{“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”:}}
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at Dgp (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9123:32291)
at AQi.waitForProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9123:37347)
at async lba._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:3913)
at async fAe (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7918:12023)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:8049
at async fAe (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7918:12023)
at async lba.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:7973)
at async lba.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20487:23432)
at async VIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9229:2399)
at async wk (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:19518:83910)

Does this stop you from using Cursor

Yes - Cursor is unusable

[mohitjain (Mohit)]

This is a client-side issue, not your account or our servers. The error (ERROR_EXTENSION_HOST_TIMEOUT / “Agent Execution Timed Out”) means Cursor’s extension host didn’t finish starting up on your machine. The skills/rules/commands stuck on “Loading…” and the 0% usage all rely on that same extension host, so they’ll come back once it starts normally.

Try these in order (macOS):

1. Restart the extension host: Cmd+Shift+P → Developer: Restart Extension Host. If that doesn’t do it, click Reload Window on the error, or fully quit (Cmd+Q) and reopen.
2. Update to the latest version (Cursor menu → About Cursor to check). Updating has cleared up this exact “skills stuck loading + timeout” combo for others.
3. Test with extensions disabled: Cmd+Shift+P → Extensions: Disable All Installed Extensions, then reload. A stuck third-party extension can block the host.
4. If your project has a very large working tree (thousands of changed files or big binaries), try opening a smaller folder. A heavy workspace can push startup past the timeout.
5. If you’re on macOS 26 (Tahoe), open Terminal and run codesign -vvv --deep /Applications/Cursor.app. If it reports the signature is invalid, do a clean reinstall from the DMG (not an in-app update).
6. Add Cursor to any antivirus / endpoint-security exclusions on your machine.

If it’s still happening after that, reply with a fresh Request ID (with Privacy Mode off) plus the Output → Extension Host log (View -> Output, then pick “Extension Host” from the dropdown) so we can pinpoint where startup is failing. Here’s how to grab a Request ID: Reporting a bug