Safeguard
Product•

Cursor Pro is now a legacy plan: what happens when usage runs out?

As of 18 Oct 2026 Cursor lists Pro as a legacy plan. Current plans use a weekly allowance with top-offs. What that means for security work in the editor.

Safeguard Security Team
4 min read

As of 18 October 2026, Cursor's pricing page no longer lists Pro among its current plans. Its docs call Pro a legacy plan that keeps working as it is, and say legacy plans use on-demand usage instead of top-ups. Current plans run from Free to Ultra, with a weekly allowance you can top off.

Everything below comes from Cursor's pricing page and docs, fetched on 18 October 2026. Prices exclude taxes and change often, so check the page before you buy.

Is Pro still a plan?

Cursor's account docs list Pro among "legacy Cursor plans" that "keep working as they are." They give no price and no usage figure for Pro on that page, and the current pricing page does not show it. If you are on Pro, your plan continues. If you are choosing now, you will choose from the current list.

The docs say legacy plans have two monthly usage pools, one for Cursor models and one for other models, and use on-demand usage instead of top-ups. They do not describe, on the page we fetched, exactly what happens beyond that, so read your own account settings for the rules that apply to you.

What do current plans look like?

The pricing page lists these published prices per month:

  • Free: $0
  • Plus: $8
  • Premium: $30, labeled the most popular
  • Super: $100
  • Ultra: $200
  • Teams: from $30 per user
  • Enterprise: custom

Each paid tier has a usage pool, with Plus at 1x, Premium at 4x, Super at 15x and Ultra at 50x. The page says the pool is shared across Cursor and Grok, and that the allowance refreshes weekly. Third-party models are not in the allowance. They are billed separately at API list price, and you can set spending caps.

What happens when you hit the limit?

On current plans the page gives two options: buy top-offs, or wait for the weekly refresh. Remaining usage is shown in settings.

For security work, the practical effect is timing. A large code review or a long agent session can use a lot of allowance in one sitting. If you hit the limit during an incident, you either pay to continue or lose the assistant until the refresh.

Which security tasks suit a limited plan?

Spend the allowance on tasks where a model adds judgment, and use deterministic tools for the rest.

  • Good fit: explaining a finding, drafting a fix for one function, reviewing a diff for a specific bug class.
  • Poor fit: scanning an entire repository by pasting files into chat. A scanner does that faster, cheaper and repeatably.

Safeguard's MCP server at mcp.safeguard.sh can be connected to Cursor, and Safeguard tool calls are unlimited on every Safeguard plan. That moves the lookup work, such as "which projects use this package," out of your model allowance and into tool calls. The model still uses allowance to read the results.

What to do

  1. Open your Cursor settings and note the plan name, the allowance and the refresh date.
  2. If you are on Pro, ask Cursor support what rules apply to your plan.
  3. Decide a rule for incidents: who may buy top-offs, and up to what cap.
  4. Set a spending cap for third-party models.
  5. Move inventory and lookup questions to tools, and keep the model for reasoning.
  6. Re-check the pricing page monthly, because plan names move.

Quick check

Can I still buy Cursor Pro?

The current pricing page does not list it. The docs describe Pro as a legacy plan that keeps working. Check with Cursor for current availability.

Do third-party models use my allowance?

No. The pricing page says they are billed separately at API list price, with spending caps you can set.

Sources

Last reviewed: 18 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.