Cursor IDE
Local agent, Grok 4.6, it happens I would say since 3 days ago, very annoying.
Open a new chat and just prompt anything.
MacOS
3.17.21 (Universal)
Cursor Grok 4.6
No - Cursor works, but with this issue
+1 from me. I was raving about the speed and balance of the cursor-grok models. Then all of a sudden several days ago the speed slowed by like 5x. Seems to be the case regardless of 4.5 vs 4.6, and any thinking level.
Hey @angel-luis, thanks for the report, and thanks @Jonnoh for the extra confirmation.
The “Taking longer than expected” message appears when the model takes a while to start responding. Grok 4.5 and 4.6 have been under very heavy demand recently, and during busy hours responses can take noticeably longer to start. This is on our side, not related to your setup or account.
We have been rolling out capacity and routing improvements over the past few days, and response times have been improving steadily today!
Thank you, have to note that “Continue Working” is the most used thing now in Cursor, is really annoying this situation, it doesn’t even notifies, as UX I would put it automatically in those situations, you can’t rely now in put a task and do other things meanwhile.
Well this is a different issue, this is the issue for this error: Failed to move agent root
+1 I am experiencing this as well. Very annoying.
I’ve been experiencing the exact same problem for the past 6 hours. Whenever a conversation has even a slightly substantial context (around 150K or so), it ends up like this—trapped in an infinite “Taking longer than expected…” loop. If you wait long enough, you’ll eventually get a 503 error.
Hey @thibauld and @q1438998005, thanks for the extra reports.
@thibauld, what you hit this afternoon lines up with a provider issue affecting all Grok models that started around 13:20 UTC today. You can follow the status at status.cursor.com.
@q1438998005, a few things are stacking up for you:
Thank you @Colin . It got better but then lately it started coming back… it’s very frustrating because it’s totally unclear how to fix it (besides rebooting the machine 
).
Here is the ID of the latest request that did that for me: 61a55519-9e50-494a-8ad7-2e79a7677668 
Update: still stuck after writing this message… I think my chat is bricked 
If I stop everything and ask something else in the chat… it is just dead
Update 2: Restarting Cursor restored the usability of the chat
Here we go again… it just happens way too frequently
I have 3 agents running:
2 out of 3 are stuck…2 out of 3 are stuck:
Request ID bfc26b5f-197d-40ca-8f31-c7d99294d52b 
Request ID f6e8f89b-f0dd-46f2-a6e1-ea1d435eb1d9
It’s a really a huge productivity killer…
My setup: Windows 11 + WSL2 (all 100% up-to-date)
Version: 3.19.19 (user setup)
VS Code Extension API: 1.128.0
Commit: 6496ea8a068aebfcd21990e70ff522e9abf10c80
Date: 2026-09-08T16:25:33.352Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200
EDIT: This time restarting Cursor didn’t help… both bricked chats before restart are still bricked 
Hey @thibauld, thanks for the request IDs, they were exactly what we needed.
None of the three requests ever reached our servers. The message got stuck inside Cursor on your machine before it was sent, which is why nothing came back and why restarting was the only thing that helped.
I would suggest upgrading to v3.20 to check if the issue persists. If so, please start a new thread!
This thread was started during some heavy load on the model side at the end of August. To avoid this becoming a catch-all thread, I’m going to close it.
