After the recent Aug 6, 2026 update, while doing a small web UI fix with Grok High/Fast, Cursor seems to be stuck in some sort of loop, with the client periodically going dark and then reloading, and no code changes apparent. I stopped it and did a Developer:Reload Window (Command Palette). Claude Sonnet reports others have reported this as well, and suggests a non-Grok model.
Use Grok High/Fast to make a UI change triggered by a read from an Azure table.
Expected Behavior
I expect that Cursor Grok High/Fast would not go into an infinite loop and would make the desired UI changes. The screenshot shows the code changes count never changed on each loop iteration.
Hey, thanks for the detailed report with the screenshot and version, that really helps. There are actually two separate things here.
About loop with no code changes. Based on the screenshot, your agent did apply the edits, the Files Changed card shows that. The loop happened because of verification. The agent got stuck on the local dev server, which kept serving an old version of games.js (it even says that in the bubble). On each iteration it saw the old file and tried again. To break the cycle:
Restart your local dev server, or disable its cache or do a hard refresh so it serves the latest file.
Or stop the agent and give an explicit instruction, which is basically what you did via Reload Window.
About the client freezing and then reloading. That’s a separate issue. These are freezes from Extension host unresponsive that can show up in heavy sessions (lots of MCP, browser, and shell calls in a row). We’re tracking it, but I can’t share an ETA yet. Reload Window was the right move here.
If the freezes happen again, tell me which MCP servers and extensions you have enabled. As a quick test, you can run cursor --disable-extensions from the command line and or temporarily disable MCP servers to see if it’s tied to a specific one.
Let me know if restarting the server broke the loop.
I have been using Cursor Pro for about 2 weeks now. I quickly used all my Sonnet credits with Pro and bought extended Sonnet credits for $50. These ran out in 2 days. Since most of the changes were UI changes, I went go Grok High/Fast. After these hiccups, Claude Pro (Sonnet, a separate subscription with Anthropic) suggested the actions I took.
I selected Composer 2.5 as my default model and was able to make and test the desired changes. I will be using Composer 2.5 going forward.
Thank you for your quick reply. I am considering Cursor Ultra. I bought a year subscription to Cursor Pro, but Cursor Ultra on a monthly basis might serve better for those months with heavy work. Sonnet is an excellent model, but expensive.
I’m not working for a company; these are my own projects so expenses must be kept down.
Glad Composer 2.5 worked out. It’s a solid pick for UI iterations, and it doesn’t burn credits like Sonnet.
About the loop: like we thought, it was verification against a local dev server that was serving an old file version, not the changes themselves. So next time, if you see Files Changed not updating on every iteration, first restart the dev server or clear the cache.
Ultra vs Pro depends on your monthly load. It helps to check the latest plan and model breakdown before deciding:
