Hey, this is a known cosmetic glitch, not a bug in your project. cursor-agent-worker is a built-in Cursor extension that only actually runs in agent windows. When you’re connected to WSL, in a normal editor window it can show as enabled but not running, so the Reload Window badge doesn’t go away even after a reload.
Main point: it’s harmless. Agent and everything else works fine, and you don’t need to remove the extension (and you can’t, since it’s built-in).
What you can try: fully quit Cursor and start it again, not just Reload Window. Sometimes that clears the badge.
Overall, this is a known issue, especially with WSL and Remote. I can’t share an ETA for a fix yet, but I logged that it reproduces on 3.8.23. You can safely ignore it.
Hey @aldinokemal quick update on this issue: the fix for the Reload Window badge that won’t clear on WSL or Remote has landed in the Cursor 3.11 release line. Once you update to that, please try again and the badge should stop showing up.
Until then, nothing changes. It’s just cosmetic, the agent and everything else work fine, so you can safely ignore it. If you fully quit and restart Cursor, not just Reload Window, it sometimes clears the badge temporarily.
Hey, this is a different bug, not related to “Reload Window” (by the way, the fix for that is in 3.11. Once you update, the badge should disappear).
About the Codex icon: this is a known regression in 3.10. The extension container doesn’t re-register in the sidebar, so the icon disappears and the view ends up under Explorer. We’ve already reproduced it and it’s being tracked separately. There’s an active thread here, it’s best to follow updates there: Codex extension disappeared from UI
What you can try right now:
Command Palette Cmd+Shift+P → View: Reset View Locations (this usually puts Codex back where it belongs)
Open a new window (or open a folder in a new window). This re-registers the icons
If Codex is currently stuck under Explorer, right click the view title → Move View back to its container
As a temporary option, you can roll back to 3.9 (the bug doesn’t reproduce there): Cursor · Download
I can’t share an ETA for the fix yet. Let me know if none of these workarounds help.
I can’t share an exact release date for 3.11. We’re doing a staged rollout, so some users will get the version earlier and others later. I don’t have a firm ETA yet.