Hey, thanks for the detailed report. This isn’t a bug, it’s expected behavior. Right now on the Free plan without your own API key, the model picker is locked to Composer 2.5 Fast with a lock icon. That’s why Auto shows for a second when you open it, then switches back to Composer 2.5 Fast. That’s by design.
Main thing, the lock doesn’t disable AI. Composer 2.5 Fast is our own fast model, and it fully works on Free. On your account, requests are going through and usage is being counted normally, so AI features are available, just through this model.
The lock icon only means you can’t change the model to Auto or others unless you upgrade to Pro. If you need model selection, that’s on Pro.
Let me know if Composer 2.5 Fast actually stops responding or errors out. If it does, please send the Request ID right upper corner of the chat context menu > Copy Request ID and we’ll take a look.
Thanks for clarifying, that makes it clear now. I can see the screenshot with “You’ve hit your usage limit” and the Request ID. This isn’t about the model being locked, it’s that requests are actually getting blocked.
This is a known issue. On the Free plan, some users hit the usage limit and get “You’ve hit your usage limit” even though the dashboard still shows remaining quota like yours at 51%. So the block and the dashboard percentage don’t match. We’ve logged it, but I can’t share a fix timeline yet.
If you need AI right now without waiting, upgrading to Pro should unblock the model and remove this limit. That’s not a bug fix though, we’re investigating the mismatch separately.
I am experiencing the same known issue on the Cursor Free plan.
Request ID: accd68b9-54a0-4774-9e6e-9604eb5a7816
The Cursor IDE immediately displays “You’ve hit your usage limit” and blocks Composer 2.5 Fast, but my account dashboard shows only 63% used, with approximately 37% remaining. My usage resets on August 14, 2026.
The agent stopped during an active local coding task. Please investigate the mismatch between the IDE usage enforcement and the dashboard quota.
Hey, thanks for the report and the Request ID. Yeah, this is the same known issue we mentioned earlier in the thread. On the Free plan, requests can hit “You’ve hit your usage limit” even though the dashboard still shows quota left on your side 37%. The limit enforcement in the IDE and the percentage on the dashboard don’t match.
We’re tracking it, but I can’t share an ETA for a fix yet.
If you need AI right now without waiting, upgrading to Pro removes the block. This isn’t the actual fix though, we’re investigating the mismatch separately.
I am experiencing a usage limit issue on the Cursor Free plan.
My dashboard shows 53% used, with 47% remaining, and the usage resets on August 18, 2026. However, Composer 2.5 Fast immediately displays “You’ve hit your usage limit” and I cannot send any prompts.
The request is blocked before an Agent conversation is created. The sidebar continues to show “No agents yet,” so there is no chat menu or Request ID available.
I have already uninstalled and reinstalled Cursor, but the issue remains.
Hey, thanks for the details and screenshots. I can see the overview showing 53% used and the You’ve hit your usage limit message on Composer 2,5 Fast.
This is the same known issue mentioned earlier in the thread. On the Free plan, requests can sometimes hit You’ve hit your usage limit even when the dashboard still shows quota left, in your case 47%. The limit enforcement in the IDE and the percentage on the dashboard don’t match. And yep, no Request ID makes sense since the block happens before the conversation is created, so no need to ask for it.
We’re tracking it, but I can’t share an ETA for a fix yet. Reinstalling won’t help since it’s on our side.
If you need AI right now, upgrading to Pro removes the block. That’s not the actual fix though, we’re still investigating the mismatch separately.
Hey, thanks for the detailed report and screenshots. I can see the overview showing 51% used and the “You’ve hit your usage limit” message on Composer 2.5 Fast.
This is the same known issue mentioned earlier in the thread. On the Free plan, requests can sometimes hit “You’ve hit your usage limit” even though the dashboard still shows quota left, in your case 49% remaining. The limit enforcement in the IDE and the percentage on the dashboard don’t match. The fact that you just started using Cursor but it already shows 51% used also fits this.
Reinstalling, clearing AppData, or switching networks won’t help. This is on our side, not a local setup issue. I won’t ask for a Request ID since the block happens before an agent conversation is created, so there won’t be one.
We’re tracking the issue, but I can’t share an ETA for a fix yet. If you need AI right now without waiting, upgrading to Pro removes the block. That’s not the actual fix though, we’re handling the mismatch separately.
Is there any news on this topic? I cant use cursor anymore. My account should have been reset on begin of july. It still blocks every prompt. So there are actually 2 problems:
it blocks even though the account should have 50% remaining tokens.
After one months, the account is not reset
If you want to block all free plans, this is your decision. Bur please, dont fool us. Be transparent.
Hey, thanks for coming back with an update. I’ll cover both points.
On the first one: seeing the You've hit your usage limit block while the dashboard still shows quota is exactly the issue we’re tracking. The enforcement in the IDE and the percentage on the dashboard are out of sync right now, and it’s not something in your setup. Reinstalling, clearing settings, or switching networks won’t help. There’s no intentional block on the Free plan, it’s a sync issue we’re investigating. I can’t share an ETA yet, but I’ll post in the thread when I have an update.
On the second one: if your quota didn’t reset at the start of the month, that’s specific to your account and billing cycle. The team at [email protected] can check that. Email them and they’ll look at the reset status for your account.
If you need AI right now without waiting, upgrading to Pro removes this block. That’s not the fix for the underlying issue, we’re handling the sync problem separately.
I have a similar issue.
Agent is stuck on usage limit even though account shows that my quota is not finished. Model picker is stuck on Grok 4.6 even though I disabled it from settings and I am on free plan. It doesn’t allow me to choose any other model.
Hey, thanks for the report and the screenshot. I can see the You've hit your usage limit message and the model picker locked to Cursor Grok 4.6 Medium. There are two separate things here.
First, the You've hit your usage limit block while the dashboard still shows quota. This is the same issue we mentioned earlier in the thread. The limit enforcement in the IDE and the percentage on the dashboard are currently out of sync, and it’s not something in your setup. Reinstalling, resetting settings, or switching networks won’t help. We’re tracking it, but I can’t share an ETA yet. I’ll post in the thread when there’s an update.
Second, the picker is locked to Grok 4.6 and won’t let you choose another model. That’s expected on the Free plan without your own API key. The model is fixed, and you can’t change it without Pro. That’s why the “disable model” setting doesn’t work here, the lock overrides it.
If you need AI right now without waiting, upgrading to Pro removes the block and unlocks model selection. That’s not a fix for the main issue though, we’re investigating the sync problem separately.
Hello. I am using Cursor on Windows with a Free Plan (First of all, I want to clarify that I’m currently using the Free plan, but only for now, because I’m considering upgrading to the Ultra plan. Therefore, when you receive this message, I may still be using the Free plan, or I may have already upgraded to the Ultra plan. Please check this. This error occurred while I was on the Free plan. How you help me resolve this issue will affect my decision about changing my current subscription plan).
My Plan & Usage dashboard still shows approximately 57% Included Usage, but every Ask/Agent request immediately returns “You’ve hit your usage limit”.
I restarted Cursor and the problem remains. I found reports from other Free Plan users describing the same mismatch between the dashboard usage percentage and IDE limit enforcement.
Could you please confirm whether my account is affected by this known Free Plan usage-enforcement issue and whether access to the remaining included usage can be restored?
I can provide screenshots, my Cursor version and a Request ID if one is available.
Hey, thanks for the report and the screenshots. I checked your account.
The limit you hit on the Free plan triggered correctly. Your included usage for the month really was used up by requests sent on September 4, and a Grok 4.6 session used a noticeable amount of tokens. So unfortunately there isn’t any remaining usage we can restore.
What’s confusing is the percentage shown on the Plan & Usage page. Right now that counter underreports usage on the Free plan, so it can show around 50 to 60% even when you’ve actually hit the limit. This is a known display issue and we’re tracking it. The limit itself is working correctly.
I also see you already upgraded to Pro and requests have been going through normally since then. If you later upgrade to Ultra, your included usage scales up further and the models stay the same. Let me know if anything else looks off.
Hey, thanks for the details. I checked your account.
Your included usage on Free for the current cycle was used up on September 3, requests to Auto and Grok 4.6 used it up that day. So the limit message since then is expected. Also, the 43% you see is the chat’s context window, not plan usage. It’s a different counter.
Free usage resets on September 7, after that your requests will start working again. If you need to keep going sooner, upgrading to Pro removes the limit right away.
One more thing. The Free usage percentage on the dashboard currently underreports real usage, so it can show remaining usage even when the limit is already hit. This is a known display issue we’re tracking. The limit itself is working correctly.
