Can someone do something about the app crashing all day ling since last night. I am using the desktop app I can’t get any work done
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)?
- Cursor IDE
- Cursor CLI
- Background Agent (GitHub, Slack, Web, Linear)
- BugBot
- Somewhere 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 aboutin 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, thanks for the report. I’ll need a bit more info to understand what’s going on:
- What OS are you on (Windows/Mac/Linux)?
- Your Cursor version (Help > About Cursor > Copy)
- Does it crash right on launch, or while you’re using it? If it’s while you’re using it, what actions trigger it?
- Do you see any error messages?
While we wait, try starting it from Terminal:
cursor --disable-extensions
If it works like that, it’s most likely an issue with one of your extensions.