Does Cursor's on-demand spending limit actually prevent usage beyond the configured amount?

Support Help
1

I’m raising a technical question about how Cursor’s on-demand spending limits are enforced.

I configured a manual spending limit of $16 and disabled on-demand usage. However, the dashboard subsequently displayed more than $600 in usage.

My question is not about requesting a refund or discussing private billing details. I already have an open support ticket for that.

I’m asking about the technical behavior of the spending limit because this is relevant to anyone using Cursor:

1. Is the manually configured spending limit a hard cap or only a notification threshold?

2. Can usage continue accumulating after on-demand usage has been disabled?

3. Can delayed usage reporting cause the displayed consumption to exceed the configured limit?

4. Is there a way for users to guarantee that usage cannot exceed a specific amount?

5. If a spending limit is changed, when does the new limit become effective?

I believe these are legitimate product questions that deserve a clear, public explanation.

Developers need to understand whether the spending controls can be relied upon to prevent unexpected costs.

I’m not requesting account-specific assistance here. I’m asking how this feature is designed to work.

I would appreciate an official technical explanation from the Cursor team, as well as experiences from other users who have encountered similar behavior.

7

Hey @escb77,

1. Hard cap. When on-demand spend hits your limit, new requests are blocked until you raise it or the next cycle starts. Spend alerts are the separate notify-only feature; Spend limits are what actually cap spend.

2. No new usage once on-demand is off. Only a request already in flight can finish.

3. Only slightly. Enforcement isn’t instant, so the total can land a bit over (in-flight work bills on completion, and the dashboard lags a few minutes). That’s a small overshoot, never a large multiple of your limit.

4. Keep on-demand off, or set a fixed limit rather than “No Limit”, and make sure only you can sign in, since anyone signed into the account can change this setting.

5. Immediately. (Raising a limit mid-cycle can rebill overage that was previously credited.)

A large overrun past a small limit with on-demand off isn’t something reporting lag causes; it usually means the limit got switched to “No Limit”. Since anyone with account access can do that, I’d secure your login (change your Google/GitHub/email password and turn on 2-step verification there) and revoke any sessions you don’t recognize at cursor.com/dashboard → My Settings → Active Sessions (guide). The team on your existing ticket can review the specific charges.