I’m using the cursor desktop app. It said it was taking a long time, but it’s been over a day and it’s still stuck. I can’t get it to respond. I’ve tried “Continue working”, loging out and in again, other projects. On other projects it says “Taking a little while…”, but never get past that. I’ve been dead in the water for over a day now.
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 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 @Holden_Caine, thanks for the report, and sorry you have been stuck for so long.
The chat you were working in got stuck in a “still generating” state on Wednesday afternoon (around 1:30 PM Mountain). Everything you have sent since then, including Stop and Continue Working, has been queuing up behind it in the app, so those messages are not reaching our servers. A normal reopen this morning did not clear that, and the “Taking a little while…” spinner on other projects looks like the same stuck app rather than a separate problem. That chat is also a very long one, which may be part of why it got stuck.
Can you go ahead and see if these issues replicate with a fresh chat? If the new chat responds, right-click the stuck chat in the sidebar and choose Archive. Its history stays available, but it will no longer block the app. Start a fresh chat for that work and reference the old one if you need the context.
If the new chat also gets stuck on “Taking longer than expected”, or a project sits on “Taking a little while…” for more than 30 seconds, open the command palette (Ctrl+Shift+P) and run “Developer: Capture and Send Debugging Data” with the default options please! *
*