Agent execution timed out and don't loading profile information

[KPD (Пётр К)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Today, the cursor suddenly stopped working, accompanied by the following errors:

1. It fails to establish a connection in the chat. Agent execution timed out
2. It doesn’t load profile information, yet it indicates that I am logged in. It prompts me to upgrade to Pro, even though I already have a Pro subscription.

Steps to Reproduce

I’m getting this error constantly now.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.14.7 (user setup)
VS Code Extension API: 1.128.0
Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0
Date: 2026-07-30T06:41:34.009Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19044

For AI issues: add Request ID with privacy disabled

Request ID: 1a0d4781-b10a-4da3-a42c-351130682266
{“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”:}}
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at $vp (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9596:38262)
at ooi.waitForProviderRegistration (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9596:43695)
at async bml._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18929:4327)
at async z2e (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8484:11978)
at async vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18929:9084
at async z2e (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8484:11978)
at async bml.streamFromAgentBackend (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18929:8981)
at async bml.getAgentStreamResponse (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18929:31582)
at async V7e._submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9665:2569)
at async V7e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/%D0%A0%D0%90%D0%91%D0%9E%D0%A2%D0%90/AI/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9656:78033)

Does this stop you from using Cursor

Yes - Cursor is unusable

[KPD (Пётр К)]

This solution helped:

The topic can be closed.

[deanrie]

Hey, thanks for the detailed report with logs and the Request ID. That helped a lot.

Both symptoms come from the same root cause. The extension host in your main window got stuck and did not register providers. Because of that, chat returns Agent Execution Timed Out, and the profile page cannot load your subscription so it falls back to showing Upgrade to Pro. Just to clarify, your Pro account is active and your payment is fine. This is only a display artifact when the profile did not load. Once the window reconnects, Pro will show again.

What to try, in order:

1. When you hit the timeout, run Ctrl+Shift+P then Developer: Restart Extension Host, or Reload Window. A new chat usually works after that, and you can bring context over via @Past Chats.
2. Your logs show network errors NGHTTP2_REFUSED_STREAM about every 10 minutes. This looks like local HTTP/2 interference from antivirus, proxy, or TLS inspection. Try this:
   • App Settings Ctrl+, then search HTTP/2 then enable Disable HTTP/2.
   • In your antivirus or proxy, add the Cursor install folder and %APPDATA%\Cursor to the whitelist.
3. If timeouts keep happening after that, run cursor --disable-extensions from the command line. If the issue goes away without extensions, one of your installed extensions is likely hanging the extension host.
4. During a timeout, run Ctrl+Shift+P then Developer: Open Process Explorer and check the extensionHost process. If it is stuck with high CPU, that confirms the extension host is hanging.
5. If you decide to reinstall, note that a normal uninstall does not remove %APPDATA%\Cursor. Delete that folder manually before a clean install.

A similar case is discussed here: Frequent "Agent Execution Timed Out" errors during agent chats

Let me know how it goes after these steps. If the timeouts keep happening, please send a fresh Request ID.