I want to document a recurring state-persistence bug in the dashboard settings.
The Issue:
When a billing cycle rolls over, user-configured spend limits or preference states occasionally fail to persist or get silently overridden. Even when restrictions are previously saved, the system can behave as if limits were reset, leading to unexpected resource consumption outside the primary subscription quota before users notice.
Steps to observe:
Set specific limit configurations or preferences in the dashboard.
Let the account reach a billing cycle renewal point.
Check whether the previous state configuration has persisted or reverted to default behavior.
Workaround found so far:
To completely stop this unexpected behavior, users currently have to manually toggle and re-save or entirely disable related options in the dashboard settings to force state synchronization.
Has anyone else experienced configuration states resetting automatically upon cycle transitions?
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey, thanks for the detailed report. I dug into what’s happening, and it’s not related to the billing cycle.
Your spend limit and on-demand settings don’t reset when a cycle changes. When the server rolls over to a new cycle, it doesn’t raise the limit. Each time the limit “went back” to Unlimited, it was a deliberate settings change made from a session logged into your account on a device you don’t normally use, and that same session then used models on-demand. Your own changes from the web dashboard (lowering the limit and turning off on-demand) were saved correctly every time.
This looks like someone else has access to the account, either a shared login or unauthorized access. I’d recommend doing this right now:
Open cursor.com/dashboard > Settings > Active Sessions and click Revoke for any devices you don’t recognize. Revoking can take up to about 10 minutes.
Change the password on the Google account you use to log into Cursor, and enable 2-step verification.
Keep on-demand usage OFF, or set a fixed monthly limit instead of Unlimited.
If you’re sharing a login with someone, each user needs their own Cursor account. Shared access is exactly what can make it look like the setting is changing by itself.
Once the extra sessions are removed, the setting will stay exactly as you saved it. More account security info: Compromised account | Cursor Docs
If you want us to look at a specific on-demand charge, email [email protected] and the team will review it on your account.