Cursor agent often have network issue

[habaohaba (linzhuo)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When i use agent in cursor, does it need extension to respond? Why I not directly use cc in terminal since it is more network reliable.

Steps to Reproduce

just use agent

Expected Behavior

repond

Operating System

Linux

Version Information

Version: 2.6.12 (Universal)
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, the agent doesn’t require any extensions to work. It should work out of the box.

To help figure out what’s going wrong with the network, a few things to check:

• Run the network diagnostics: Cursor Settings > Network > Run Diagnostics and share the results here.
• What exact error do you see when using the agent? “Taking longer than expected”, “Connection lost”, or something else? A screenshot would help.
• Try disabling HTTP/2. Add this to your settings.json (Cmd+Shift+P > Preferences: Open User Settings (JSON)):

  "cursor.general.disableHttp2": true
  

  Then restart Cursor.
• Are you on a VPN, proxy, or corporate network?

Let me know how it goes.

[habaohaba (linzhuo)]

It say waiting for extension host. I don’t know what does this mean.

[deanrie]

“Waiting for extension host” is a different issue from network problems. The agent depends on the extension host process, and if it hangs or crashes, you’ll see this error.

A few things to try:

1. Disable all extensions and test the agent: run cursor --disable-extensions in Terminal, then try using the agent.
2. Check if a specific project triggers it: open a new, empty folder and test there. If it works fine, the issue might be project-specific.
3. Open the Process Explorer (Cmd+Shift+P > Developer: Open Process Explorer) and check if extensionHost is using unusually high CPU or memory.

Also, your OS info shows macOS (Darwin arm64), not Linux. Just want to confirm you’re running locally and not through any remote connection (SSH, WSL, etc.)?

This is a known issue the team is tracking. Let me know what you find from the steps above.

[habaohaba (linzhuo)]

I ssh connect to a linxu server.

[deanrie]

Got it. SSHing into a Linux server explains the “Waiting for extension host” issue. This is a known problem that happens more often over SSH, especially with larger workspaces.

A few things to try:

1. Open a smaller subfolder instead of the root of a large project. This is usually the best workaround since the extension host has less to scan on startup.

2. Add a .cursorignore file to exclude heavy folders Cursor doesn’t need to index, like build outputs, node_modules, or large data directories. It works like .gitignore.

3. Test with extensions disabled. Run cursor --disable-extensions and see if the agent works. If it does, an extension is likely causing the extension host to hang. You can then turn extensions back on one by one to find which one.

4. Check Process Explorer. Open Cmd+Shift+P, then run Developer: Open Process Explorer. See if extensionHost is using a lot of CPU or memory.

The team is aware of this pattern with SSH connections. Can you share how big the remote workspace is, like the rough file count or total size? That would help narrow it down.