Home / Cursor
Coding · Anysphere ✓ Verified Jun 2026 Last audited: 2026-06-29

Cursor:
What the pricing page doesn't tell you

Based on public docs, community reports, and third-party benchmarks — not legal advice or official statements.

Hidden Behaviors
0
documented & verified
Transparency
41%
of key policies disclosed upfront
Last Verified
Jun 2026
$20/mo · Cursor Pro
Hidden Behaviors
4 documented

Behaviors confirmed through user reports, help docs, and independent testing — none disclosed on the pricing page.

01 ⬤ Critical Impact
Overage billing is ON by default — card charged automatically
Official
Documented in billing settingsCursor's billing docs confirm overage charges apply once credits are exhausted, unless a spend cap is set manually.
Observed (community)
Surprises heavy users mid-monthCommunity reports of unexpected charges when switching to frontier models (Claude Opus, GPT-5) that burn credits faster than Auto mode.
Estimated (not verified)
Easy to trigger unknowinglyA session using Claude Opus 4.5 can consume the same credits as several sessions on Auto — with no in-editor warning before overage kicks in.
02 ⬤ Critical Impact
Credit pool shrank ~40–60% since June 2025 — price unchanged
Official
Confirmed in June 2025 changelogCursor shifted from a flat 500 fast-requests/month to a $20 credit pool. Official changelog acknowledges the restructure.
Observed (community)
Community estimates 200–300 requests at current model pricesBased on community billing analysis — actual count varies by model selected.
Estimated (not verified)
Frontier model users hit hardestDevelopers who regularly use Claude Opus or GPT-5 may get 100–150 requests before hitting limits.
03 ⬤ Medium Impact
Credit dashboard doesn't translate to 'requests remaining'
Official
Credit consumption shown in billingCursor shows credits spent, but no 'requests remaining' counter — users must estimate based on per-model costs.
Observed (community)
Most users don't do the mathCommunity reports suggest most developers don't monitor credit consumption until they hit a wall or receive an overage charge.
Estimated (not verified)
Harder to plan than flat-request systemsPrevious 500 fast-request model made planning trivial. Credit-based math requires knowing per-model cost, which isn't surfaced in the editor.
04 ⬤ Low Impact
Privacy Mode is off by default — code stored on Cursor servers
Official
Documented at cursor.sh/privacyPrivacy Mode prevents code from being stored on Cursor's servers. Must be manually enabled in settings.
Observed (community)
Default behavior stores codeWithout Privacy Mode, code context sent to Cursor may be stored for product improvement purposes, per privacy policy.
Estimated (not verified)
Enterprise users at highest riskDevelopers working on proprietary codebases may be sending sensitive code without realizing storage is active.
Real Limits
Cursor Pro
$20/mo · Cursor Pro
Reset Cycle
Monthly — resets on your billing date, not the 1st of the calendar month
Stated Cap
$20 credit pool (Pro) — community estimates ~200–300 requests at standard models, fewer on frontier
Usage Meter
Credit consumption shown in billing settings — not translated to 'requests remaining'
Overage
ON by default — card charged at API rates once credits run out unless manually capped
Privacy Default
Privacy Mode is OFF by default — code context may be stored unless manually enabled
⚠ Overage billing active
Unless you set a manual spend cap in settings, exhausting your $20 credit pool starts charging your card at API rates automatically — with no in-editor warning.
Policy History

Confirmed changes at the same price — documented with source type and dates.

Jun 2025
Fixed 500 fast-requests/month replaced by $20 credit pool — community estimates ~200–300 requests (40–60% effective cut), price unchanged
OFFICIALcursor.sh/changelog, June 2025 billing restructure
Jun 2025
Overage billing turned ON by default — card charged automatically when credits run out unless manually disabled
OFFICIALcursor.sh/pricing — overage billing documented in billing settings
Who It's For

Same data, different verdict depending on how you use it.

✓ Works well for
Daily professional coding
$20 credit pool covers most developers who code steadily across the month.
Codebase-aware AI
Reads your entire repo — not just the file you have open.
VS Code migrators
Drop-in fork — extensions, keybindings, settings transfer instantly.
✗ Problematic for
Frontier model power users
Choosing Claude Opus or GPT-5 burns credits 2–3× faster than Auto mode.
Predictable billing
Overage billing ON by default — card charged automatically if credits run out.
Occasional coders
If you code fewer than ~5h/week, free tier likely covers your needs.
Transparency Breakdown

How much is disclosed about each dimension — before you pay.

Real Headroom OFFICIAL · cursor.sh/changelog
~200–300 requests estimated (community) — down ~40–60% since June 2025. Frontier models cost significantly more per request.
community estimate, varies by model
Response Speed ESTIMATED · editorial
Depends entirely on selected model — Tab completions near-instant; premium model chat mirrors underlying model latency.
no independent Cursor benchmark
Limit Transparency OFFICIAL · cursor.sh/settings
Credit dashboard exists but doesn't show 'requests remaining' — requires manual math. Overage billing not prominently flagged.
credits shown, requests not
Data & Privacy OFFICIAL · cursor.sh/privacy
Privacy Mode available but OFF by default. Enabling it prevents code storage. Not surfaced during onboarding.
opt-in required
Reliability OFFICIAL · cursor.sh/status
~1 incident/30d — ~99.5% uptime (est.). Status page available.
status page public
Overall Transparency Score ⓘ HOW?
Weighted estimate — see methodology for formula
41%
Compare Transparency
Visit Cursor
Frequently Asked
Did Cursor Pro get worse without a price change?
Yes. In June 2025, Cursor replaced a flat 500 fast-requests/month with a $20 credit pool — community estimates suggest ~200–300 requests at standard model prices, a real reduction at the same $20 price.
Will Cursor charge me extra automatically?
Yes, by default. Overage billing is on unless you manually set a spend limit in settings. Exceeding your credit pool can result in charges at API rates.
How do I know how many requests I have left?
Cursor shows credit consumption in billing settings, but doesn't translate it into a request count — you need to estimate based on which models you use and their per-request credit cost.
Is my code private by default?
No. Privacy Mode is off by default. To prevent code from being stored on Cursor's servers, enable Privacy Mode manually in settings.
Get alerted when policies change

We track silent limit cuts before most users notice them.

How we audit — full methodology and source classification