Agents Randomly Failing

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I send a message and get no response. Open developer tools and there are lots of red, angry error messages.

incredibly frustrating that there’s no ui feedback for this.

spans collection is not enabled for this user"}“}
mdf @ workbench.desktop.main.js:12123
workbench.desktop.main.js:55 ERR [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:”{"error":"Trace spans collection is not enabled for this user"}“}
error @ workbench.desktop.main.js:55
workbench.desktop.main.js:12123 [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:”{"error":"Trace spans collection is not enabled for this user"}“}
mdf @ workbench.desktop.main.js:12123
workbench.desktop.main.js:55 ERR [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:”{"error":"Trace spans collection is not enabled for this user"}“}
error @ workbench.desktop.main.js:55
workbench.desktop.main.js:12123 [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:”{"error":"Trace spans collection is not enabled for this user"}"}

Steps to Reproduce

step 1: use cursor normally.

Expected Behavior

the agents should respond.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Claude 4.5 Haiku
GPT 5.2 Normal

For AI issues: add Request ID with privacy disabled

64bc1be6-84d4-4f24-ab1e-6a9f1fd7421f

Does this stop you from using Cursor

Yes - Cursor is unusable

2

I wasted over 50 dollars today with stupid bugs and issues like this one!

3

Hey, thanks for the report. The error OTLPExporterError: Bad Request with the message "Trace spans collection is not enabled for this user" indicates a telemetry issue on the backend of Cursor. It doesn’t directly affect the Agent’s operation but could be a symptom of deeper account settings issues.

In the meantime, try:

  • Restarting Cursor completely (Cmd+Q, then reopen)
  • Checking service status: Settings > Network > Run Diagnostics
  • Trying a different model
  • Clearing the cache: close Cursor, delete ~/Library/Application Support/Cursor/Cache, then restart

OTLP errors are internal telemetry for Cursor and shouldn’t block the Agent’s operation. If the Agent is truly unresponsive (rather than just showing console errors), that’s a separate issue. You could try starting a new chat (Cmd+N) to see if the Agent works there.

I’ll pass this to the team with the Request ID to check telemetry settings on the server side.

4

Its so annoying. Happening multiple times every day. Tool call ended before result was received.