Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Cursor error

Cursor: Agent Execution Timed Out

Error message
Agent Execution Timed Out

Status: 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

  1. Fix 1.

    Collect logs before changing anything: press Cmd/Ctrl+Shift+P and run Developer: Export Logs..., then select Main, Window, and Extension Host.

    YAML
    Developer: Export Logs...
  2. 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.

  3. 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/
  4. Fix 4.

    To identify active security products on Windows, run the documented commands in an Administrator PowerShell window.

    Snippet
    Get-CimInstance -Namespace root/SecurityCenter2 -ClassName AntiVirusProduct |
      Select-Object displayName, pathToSignedProductExe
    fltmc
  5. 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 errors

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.