Version: 3.25.9
VS Code Extension API: 1.128.0
Commit: 5d4df965746c5d09740842fc0f1331ba1c157830
Date: 2026-10-15T21:52:24.891Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.11.14
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Linux x64 7.2.8-9-omarchy
Just stuck here for the last couple of hours with no progress or anything else responding
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?
Where does the bug appear (feature/product)?
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
Version Information
agent about in your terminalIDE:
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?
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
hm… I restarted cursor and suddenly the reply was there including the messages I tried to send before
so it seems the UI just stopped responding but the three dots kept moving as if it was still working on something
Also getting the same issue,
Shows as: Planning next moves, but it had come back and notified me it was done. Switching projects or conversations doesn’t show me the response. I have to quit Cursor and re-open it.
Version: 3.26.16 (Universal)
VS Code Extension API: 1.128.0
Commit: 8fcb8ace5c73fa31f2e2707fd6783160e4ed3e40
Date: 2026-10-21T09:02:57.211Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.11.16
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0
Hey @Oscar_Garza,
Thanks for following up, and you read it right. On our side, the agent finished your first request about 4 minutes in and also answered the two follow-ups you sent afterwards. The Agents Window stopped picking up the agent’s updates partway through the first turn, so it never saw the run finish and kept showing “Planning next moves”. That’s why restarting showed everything.
This is a known issue we’re already tracking, and I’ve added your report to it. It’s caused on our side, so updating Cursor isn’t expected to change it.
If it happens again, you don’t need a full restart. Either of these should show the real state:
If you send a follow-up while it still shows “Planning next moves”, it may look stuck, so reloading first is the safer option.
@voluum, thanks for the details. It’s the same issue on your side, and the same steps should help.