in the IDE, “Accounts” wheel in the bottom-left corner is greyed out ("No accounts requested yet), but the Account is correctly recognized/shown in the Agents View
cursor_agent extension has been trying to update several times in a row. “Restarting extensions”, closing/reopening Cursor had not helped (i had C++ extension pack installed).
Only “Composer 2.5 Fast” is available as a model; “Auto” is not. It took 2 small requests to get “Exceeded your quota”…
Hey, thanks for the detailed report. Point by point, these aren’t bugs, this is expected behavior, so let’s go through it:
The Accounts widget is gray and shows No accounts requested yet. That’s VS Code’s built-in accounts system for things like Settings Sync and GitHub. It’s not related to your Cursor sign-in. Your Cursor account is fine, that’s why you see it in Agents View. This widget will stay gray until some extension requests an account, and that’s normal.
The cursor_agent extension is trying to update in a loop. This can happen on the first install and usually fixes itself after the initial setup. If it stays stuck for a long time even after a restart, let me know.
You only see Composer 2.5 Fast, there’s no Auto, and you hit quota quickly. On the Free plan, only Composer 2.5 Fast is available. Auto and other models are paid plan features. Free has a very small monthly quota, so it’s possible to use it up in just a few requests.
About your question on whether this carries over to a paid plan: no. Pro and Pro+ unlock Auto, more models, and much higher limits. Your Free quota state doesn’t carry over, paid plans have their own limits.
And since everything works fine on Linux, that’s another sign there’s no issue with Cursor itself. It’s just Free tier limits.
tried disabling/enabling cursor_agent extension. Upon disabling and cursor restart, it disappeared altogether! And is not ‘findable’ in extensions…What now??
How can one get to know that 'Auto" is a ‘paid plan’ feature?? I genuinely thought a feature originally designed to reduce/hide costs would be offered on the trial/free plan…Similarly, what’s the logic behind only offering a more expensive Composer Fast (but not normal) on Free (no mention of this in the docs).? To make it gone asap (literally, 2 small requests) and force an upgrade??
cursor_agent is gone from the Extensions list. It’s a bundled Cursor component, not a Marketplace extension, so after you disable it, it won’t show up in the main list. To find and enable it again: open the Extensions panel, clear the search, and type @builtin or @disabled. Built-in or disabled extensions will show up there, and you can re-enable it. If you still can’t find it, reinstalling or updating Cursor will bring it back. Also, you don’t have to disable it. That update loop on first launch usually finishes on its own after initial setup.
How to tell Auto is a paid feature. Fair point. The docs don’t clearly say that on Free you only get Composer 2.5 Fast, and Auto plus the other models are on paid plans. I’ll pass this to the docs team so they can clarify it. In short: the model picker limit on Free is intentional, not a way to force an upgrade. Free is a small trial, and Pro and Pro+ unlock Auto, other models, and much higher limits.
Let me know if cursor_agent still doesn’t come back after @builtin or a reinstall.
yes, cursor_agent_worker continues to require to “Restart”, both when i re-enabled it and when i re-installed Cursor.
Why the model on free is Composer FAST and not the normal Composer? I couldn’t try anything - Fast consumed 2$ in 2 small requests…I couldnt even react on them…
The fact that cursor_agent_worker asks for Restart again after you re-enable and reinstall is a known cosmetic issue on Windows. It doesn’t affect Cursor at all, the agent is working and you can see it in Agents View. It’s just the icon getting stuck showing the restart request. No ETA on a fix yet, but if you want to get rid of the prompt right now:
Open Extensions with Ctrl+Shift+X
In search, type @builtin cursor-agent-worker
Click the gear icon on the extension, then Disable, then reload when it asks
The prompt will stop showing up. This is fully reversible, you can enable it again anytime from the same place.
One important clarification about the 2 dollars. On Free, we don’t charge you any money. Free has a small request quota, and you hit that quota, not a money limit. No real charges happen.
Why it’s Composer 2.5 Fast and not regular Composer or Auto is intentional for the Free plan. On Free, only Composer 2.5 Fast is available as a trial option. Regular Composer, Auto, and other models are included in Pro and Pro+ along with much higher limits. This isn’t meant to force an upgrade, it’s just how Free is set up.
Let me know if the @builtin prompt still comes back after that.
Do you suggest that it cursor-agent-worker can be disabled (without any impact on functionality)? If it is enabled and “Restarted” on Cursor start, it then only asks for another restart on the next Cursor start, not within the same session.
Its not about 2 dollars. Its that 2 requests dont allow to try anything!
Yes, you can safely disable cursor-agent-worker. It won’t affect functionality. The agent itself works independently of that prompt (you can see it in Agents View), and cursor-agent-worker only controls the Restart request window. Disable it and the prompt goes away, everything else keeps working. This is fully reversible, you can turn it back on anytime in @builtin. The fact it doesn’t ask again in the same session and only shows up after the next start is just how that cosmetic Windows bug looks. It’s been reported, no ETA for a fix yet.
Got it. The issue isn’t the price, it’s that the Free quota is too small to really try anything. That’s fair feedback, I’ll pass it to the team. Free is meant to be a small trial, but I’ll note your point that the current limit isn’t enough even for a proper test.
Let me know if the prompt still comes back after you disable @builtin cursor-agent-worker.