Why has cursor been reporting errors these past few days for b2c1d4e1-2230-4c7a-b698-37726c70f7b

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Request ID: b2c1d4e1-2230-4c7a-b698-377726c70f7b

Expected Behavior

1

Operating System

Windows 10/11

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hey @Ethan_YY. Thanks for the report and the Request ID, I checked it on our side.

This request streamed normally and had already started a tool call, then messages from your machine stopped reaching our servers. Our servers waited about 10 minutes and then ended the request due to a timeout. Over the last week, Cursor also logged many connections from you that were reset or dropped before finishing, across several Cursor versions. This points to the network path between your machine and our servers, not something inside Cursor itself.

It looks like most of the traffic is going through a VPN or proxy. Please try this:

  1. Open Cursor Settings > Network > Run Diagnostics and paste the results here.
  2. If you’re using a VPN or proxy, switch to a different server or node or temporarily disable it, then open a new chat and send a message.
  3. In Cursor Settings > Network > HTTP Compatibility Mode, select HTTP/1.0. It uses short requests instead of one long connection and usually handles unstable connections better.
  4. After the changes, restart Cursor and try a fresh chat with the agent.

If it still fails, send a new Request ID and the exact error text from the chat, like “Agent stopped retrying” or “Connection failed”. Let me know how it goes.

Now the cursor is working fine and no longer throwing this error. It might have been due to network or node fluctuations in the past couple of days, or possibly because I set up a reverse proxy within Cursor to use models like GPT.
A couple of days ago, for some reason, my Pro plan’s Cursor model usage suddenly jumped to 40%, going from 3% overnight. I’m not sure if this is normal billing behavior or a bug—could you please help me check?

Dean Rie <[email protected]> 于2026年9月3日周四 14:59写道:

Glad the errors cleared up. Like you saw, that pattern matched an unstable network or VPN path, not something inside Cursor, so switching nodes or using HTTP/1,0 helps keep those long connections alive.

On the usage request, that’s tied to your account, so our team at [email protected] is the right place to help. Send them a note and they can check the jump in your Cursor model usage.