Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Composer 1.5 /Auto on the first prompt of a brand-new chat, the DevTools console consistently shows:
an [otel.error] message (OTLPExporterError / NO_STORAGE privacy mode), and
repeated warnings such as [composer] No first token received within 2s/4s/6s/…
Then after 5 to 6 prompts later I get a Provider Error every single time I run a prompt. At this point the chat is unusable.
Steps to Reproduce
Symptom pattern:
New chats may work briefly
After sustained use / more context, Composer starts stalling (“No first token…”) and then fails with Provider Error / resource_exhausted
Expected Behavior
Composer/Chat should consistently return a streamed response (first token) within a reasonable time for normal prompts, without repeatedly stalling at “No first token received…” and failing.
The same conversation should remain usable over extended work sessions (hours of back-and-forth and project context) without eventually degrading into Provider Error / resource_exhausted.
A simple follow-up prompt in an active, context-rich chat should behave the same as a prompt in a new chat (i.e., not require restarting chats every few hours to keep the tool functional).
Cursor should either:
successfully complete the request, or
if limits are hit, clearly indicate what limit was reached and whether retrying will work (instead of showing a generic provider error marked isRetryable:false).
Since network diagnostics show successful DNS/TLS/API/Agent streaming, AI requests should work reliably under the same conditions without requiring special launch flags (–user-data-dir, --disable-extensions) to function.
Operating System
Windows 10/11
Version Information
Cursor version / environment
Version: 2.5.25 (user setup)
VSCode Version: 1.105.1
Commit: 7150844152b426ed50d2b68dd6b33b5c5beb73c0
Date: 2026-02-24T07:17:49.417Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200
For AI issues: which model did you use?
Composer 1.5 / Auto
For AI issues: add Request ID with privacy disabled
Request ID: 1779eb54-30c8-44e1-9963-5c675e7b8443 {“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true} Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment. aXt: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment. at jpA (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32115:44798) at WpA (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32115:43786) at ZpA (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32116:5088) at Ool.run (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32116:9098) at async s$o.runAgentLoop (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44360:8423) at async zOl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44408:8884) at async zOl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44408:9837) at async yLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32182:15752) at async Object.Gs [as onSubmit] (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43415:4781) at async vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43389:57281
Additional Information
Troubleshooting steps I have tried:
- Basic restart / account steps
Signed out of Cursor, fully restarted the app, and signed back in.
Restarted Cursor multiple times across the 3-day period.
- Network / connectivity checks
Tested on multiple different Wi-Fi networks over multiple days (same issue everywhere).
Made sure there were no VPNs running
Ran Cursor’s built-in Network Diagnostics. Results showed:
DNS resolution, SSL handshake, API check, ping, authentication, marketplace, and agent stream all returning Result: true.
Changed network transport setting from HTTP/2 to HTTP/1.1 (no improvement).
Checked Cursor status page; no incident shown during the timeframe.
- Extensions / MCP isolation
Disabled multiple extensions that I normally use.
Disabled all MCP servers.
Completely deleted the Cursor to Figma MCP integration (it was the only MCP server configured).
Found a separate extension issue with SpecStory:
It produced: “Error adapting bubble conversation data … Cannot read properties of undefined (reading 'length’)”
Uninstalling SpecStory temporarily improved behavior for a few prompts, but the main provider errors returned afterward.
Uninstalled almost all extensions
- Profile / state reset testing
Launched Cursor in a clean environment using a fresh user-data directory with extensions disabled:
cursor --user-data-dir “$env:TEMP\cursor-clean-test” --disable-extensions This improved stability compared to my normal environment.
Performed a full Cursor profile reset:
Backed up %APPDATA%\Cursor\User
Renamed it to User.bad so Cursor regenerated a new clean profile
Retested Composer/Chat after reset (issues still reappeared)
- Reinstall
Uninstalled Cursor completely.
Reinstalled Cursor (latest available version).
Issue persisted after reinstall.
- Log collection / reproduction evidence
Captured repeated Composer stalls:
[composer] No first token received within 2s/4s/6s/…
Captured failures that end in:
ERROR_PROVIDER_ERROR (“We’re having trouble connecting to the model provider…”)
often “Caused by: ConnectError: [resource_exhausted]”
Also observed recurring console noise unrelated to the main failure:
OTEL exporter error: “Trace spans collection is disabled for NO_STORAGE privacy mode” (400)
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
