Constent chashes when using claude as agent

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

cursor crashes a lot, since 2 days ago, tried using the updated ver. and still crashes constant, and loses part of the chat so have to rune the same chat request again and again eating my tokens, so who is going to pay for the constant wasted tokens. This should be free it has become unstable not stable. come on do you guys not test your ■■■■ before you release it. this bug is not a minor one but very noticeable.

Steps to Reproduce

just use it you will see an it is not just me have 3 others that this is happening to

Expected Behavior

stay working with no crashes

Operating System

Linux

Version Information

Version: 2.4.27
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.14.0-37-generic

For AI issues: which model did you use?

claude codex extra high, high, cursor 1, all of them

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. We’re seeing a wave of crashes after the recent updates, mostly on Windows with OOM errors. There are fewer Linux crashes at this scale, but the issue is still there.

We need a bit more info to understand what’s happening on your side:

Diagnostics:

  1. What exactly is the error when it crashes? (error text, error code, or does it just freeze?)
  2. Open Developer Tools (Ctrl+Shift+P > Developer: Toggle Developer Tools > Console). Do you see lines like [otel.error] or OTLPExporterError?
  3. Try running cursor --disable-extensions from the terminal. Does it still crash?

Possible workarounds (based on Windows users with similar crashes):

  • Rotate chats. Start a new one when the current chat gets big, especially with agent workflows.
  • Watch memory usage: Ctrl+Shift+P > Developer: Open Process Explorer, keep an eye on the renderer process.

Related threads (mostly Windows, but the pattern looks similar):

The team is aware of the stability issues after the last update, and there’s an active ticket for a fix. Share the diagnostic info so we can understand what’s specific about the Linux case.