Cursor error
Cursor: Agent Execution Timed Out
Agent Execution Timed OutStatus: WorkaroundLast verified 5 documented fixes3 sources
What it means
Cursor's extension host did not finish starting within 60 seconds, so Agent features could not initialize. The same root cause shows up as "Timeout waiting for EverythingProvider" in network diagnostics.
Causes
- The extension host did not finish starting within 60 seconds (official docs say causes vary).
- On managed or enterprise machines, endpoint security software (antivirus, EDR) is one possible cause: per-file scanning latency on the JavaScript modules the extension host reads at startup can push startup past Cursor's internal timeout.
How to fix it
- Fix 1.
Collect logs before changing anything: press Cmd/Ctrl+Shift+P and run Developer: Export Logs..., then select Main, Window, and Extension Host.
YAMLDeveloper: Export Logs... - Fix 2.
Check Output -> Extension Host (Cmd/Ctrl+Shift+P -> "Output", then pick "Extension Host"). If it is empty, take a screenshot; an empty panel is a strong diagnostic signal. Share the exported zip and screenshot with support, along with your OS and Cursor version.
- Fix 3.
If IT confirms an endpoint security agent is active, add both process and path exclusions from the Endpoint Security Configuration page. Windows paths include %LOCALAPPDATA%\Programs\cursor\ (user install), %ProgramFiles%\cursor\ (system install) and %APPDATA%\Cursor\; on macOS exclude /Applications/Cursor.app/. Then restart Cursor and test Agent.
Snippet%LOCALAPPDATA%\Programs\cursor\Cursor.exe %ProgramFiles%\cursor\Cursor.exe %APPDATA%\Cursor\ /Applications/Cursor.app/ - Fix 4.
To identify active security products on Windows, run the documented commands in an Administrator PowerShell window.
SnippetGet-CimInstance -Namespace root/SecurityCenter2 -ClassName AntiVirusProduct | Select-Object displayName, pathToSignedProductExe fltmc - Fix 5.
Cursor IDE 3.23 (Oct 1, 2026) release notes: if the extension host that powers Cursor's AI features stops responding for about a minute, Cursor restarts it automatically, so you no longer need to reload the window. The same release fixed extension hosts deadlocking at startup.
More Cursor errors
All 18 Cursor errorsTimeout waiting for EverythingProviderStatus: Workaround<filename> is too large (4MB limit)Status: By designCursor is damagedStatus: Workaroundsuspicious activityStatus: Workaroundxcrun: error: unable to find utility "mcpbridge"Status: Workaroundmissing tabIdentifierStatus: WorkaroundPrivate worker limit exceededStatus: By design{"error": "Too Many Requests", "message": "Rate limit exceeded. Please try again later."}Status: By design
Related reading
- Do Your Agent Hooks Fail Open? Claude Code vs Codex vs Cursor vs Gemini CLIA guard hook that crashes, times out or points at a missing script lets the tool call through by default in Claude Code. v2.1.295 adds onFailure: block. Here is what each coding agent does when your policy hook breaks, with real test runs.
- How to Keep API Keys Away From Your AI Coding Agent: Claude Code vs Codex vs Cursor vs Gemini CLIA deny rule on .env stops cat but not a Python one-liner. Here are the three layers that actually keep secrets out of a coding agent's context - file rules, environment scrubbing and credential masking - and what Claude Code, Codex, Cursor and Gemini CLI give you for each, with real test runs.
- Cursor Removes Dollar Costs From Usage Page: Tokens OnlyCursor removed dollar costs from its Usage page on July 31: self-serve plans see tokens only and the dashboard API zeroes cost fields, history included.
- AI Coding Agent Security Models Compared 2026: Permissions, Sandboxing, and Threat Models for Every Major ToolAI coding agent security models compared: how Claude Code, Cursor, Codex, Copilot, Aider and Windsurf handle permissions, sandboxing and prompt injection.
- HalluSquatting Makes AI Coding Agents a Supply-Chain ProblemHalluSquatting uses hallucinated repo and skill names to deliver promptware to AI coding agents. How the attack works and the harness controls that stop it.
- Securing AI Coding Agents: A Practical Threat Model for 2026Securing AI coding agents: a practical threat model for prompt injection, sandbox escapes, and hallucinated dependencies, with defenses ranked by effort.
FAQ
What does "Agent Execution Timed Out" mean in Cursor?
Cursor's extension host did not finish starting within 60 seconds, so Agent features could not initialize. The same root cause shows up as "Timeout waiting for EverythingProvider" in network diagnostics.
How do I fix "Agent Execution Timed Out"?
There are 5 documented fixes. Start with the first: Collect logs before changing anything: press Cmd/Ctrl+Shift+P and run Developer: Export Logs..., then select Main, Window, and Extension Host.
Is this Cursor error fixed?
Status: Workaround. No release removes the cause. The documented fixes work around it.
Sources
Last verified against 3 sources: official docs, maintainer replies and release notes.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.