cursor-agent-worker is causing to be more frustation then help please fix it
Hey, this is a known bug. The built-in extension cursor-agent-worker can get stuck showing an infinite “Reload Window” or “Update” prompt that doesn’t go away after reloading. It’s purely cosmetic and doesn’t affect the agent.
Workaround to remove the annoying prompt:
- Open Extensions with
Cmd+Shift+XorCtrl+Shift+X - Find
@builtin cursor-agent-worker - Click the gear icon, then Disable
- Reload the window
This is fully reversible. On some 3.7.x versions, Disable may be greyed out. In that case, there’s no manual workaround yet. The bug is being tracked, but I can’t share an ETA for a fix.
Related thread: Cursor v3.6.21 - caught in loop for "cursor-agent-worker" Reload Window
I upgraded to v3.8.11 and this issue is only partially fixed.
Out of the “2” notifications for “cursor-agent-worker” in “EXTENSIONS”, the one in my “devcontainer” is now gone, but the notification within my “LOCAL - INSTALLED” is still present. I have tried everything, close remote-connection, reload window locally, restarts, uninstall/re-install, rebuild of container, nothing helps. See attached.
I really hope we don’t have to wait another 2+ weeks for Cursor v3.9.x to fix this regression.
Hey, thanks for the update. The fix that landed in 3.8.x covered some cases, including the devcontainer side, but the leftover prompt in LOCAL - INSTALLED that you’re seeing clearly isn’t fully covered yet. I flagged this to the team along with your screenshot, and the issue is still being tracked, so I can’t share an ETA for a full fix yet.
The behavior is still purely cosmetic, it doesn’t affect how the agent works.
This is still broken in v3.9.8
Hey, quick update on this bug. A fix for the repeated “Reload Window” and “Update” prompt for cursor-agent-worker (including the one that still showed up under LOCAL - INSTALLED) is on the way and should land in Cursor 3.11. Once you’ve updated to that, can you please check again?
Just a reminder, this was only a cosmetic issue and didn’t affect the agent’s functionality.
cc @mjnowen, this applies to you too. Let me know if it still reproduces on 3.11.