@deanrie If you could take a look at this issue, I’d really appreciate it. When I opened Cursor quickly it still auto-triggered the agent multiple times and charged requests.
Hey, this is a known issue. Errored requests can show up as charged in the usage dashboard at first, but billing should auto-fix it and mark them as Errored, No Charge after some time, usually within an hour.
Check your dashboard a bit later and you should see it corrected.
A couple of things:
You’re on version 2.4.23 from Jan 29, which is pretty old. Please update to the latest version. Older clients can handle errors differently and may hit errors more often.
If the requests still show as charged after a while, email [email protected] and the team can review your account and fix the usage manually.
The team knows about this reconciliation delay. Your report and the confirmations from others in this thread help with prioritization.
I see the note about auto trigger, that’s an important point. The problem isn’t only that errored requests get billed, it’s also that the agent can loop and generate requests without you doing anything. I flagged this to the team separately.
@Liu_Zhiliu, thanks for the version info. I can reproduce it on 2.6.20 too, so it’s not just an old client issue.
@j-173, got it about the terminal bug that’s blocking you from updating. For the auto trigger issue, can you send a Request ID from one of those auto requests? You can copy it via right top corner of the chat > Copy Request ID. That’ll help us see what’s triggering the repeated requests.
On billing, the team is aware. If after reconciliation the requests still show as charged, email [email protected] and they can fix it manually.
The usage accounting issue for errored requests has been fixed in a recent Cursor update. Updating to the latest version should resolve this. If you’re still experiencing this on the latest version of Cursor, please raise a new thread and we’ll take a look.
