User aborted request. Tool call ended before result was received

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When writing documents or coding in agent mode, it is very slow and some errors may occur after a period of time:
User aborted request.
Tool call ended before result was received

Steps to Reproduce

when using agent mode.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (system setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

Request ID: e95cde9d-8d5c-448f-8711-289f618f494d
{“error”:“ERROR_USER_ABORTED_REQUEST”,“details”:{“title”:“User aborted request.”,“detail”:“Tool call ended before result was received”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report.

Let’s quickly check a few things:

  1. Settings > search “HTTP/2” > enable “Disable HTTP/2”, then restart Cursor
  2. Run in terminal: cursor --disable-extensions, a new window will open, then test the Agent. If it helps, remove the problematic extensions one by one. Working fix here: SLOW or NO response from the agent
  3. Settings > Network > Run Diagnostics - send a screenshot
  4. Create a new chat and repeat the request
  5. If you have MCP servers, VPN/proxy, or Zscaler/CrowdStrike, turn them off and test again

If the error persists, please share:

  • 2-3 recent Request IDs right after the error
  • Which tool fails and the exact steps
  • Explicitly pick a model instead of Auto and list which models reproduce it
  • Output from Help > Toggle Developer Tools > Console (red errors)
  • List of installed extensions

Let me know if disabling HTTP/2 or launching without extensions helped.

3

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.