Cursor May 2026: Model Controls, Spend Limits & Usage Analytics

Cursor's May update brings enterprise-grade controls: granular model blocklists, soft spend limits with smart alerts, and detailed usage analytics by user and product surface. Existing blocklists must migrate by June 1st.

Cursor May 2026: Model Controls, Spend Limits & Usage Analytics

TL;DR

  • Granular model access controls — block providers or specific model configs at the admin level
  • Soft spend limits with automatic alerts at 50%, 80%, 100% usage thresholds
  • Enhanced usage analytics with per-user filtering and product surface breakdown (clients, Cloud Agents, automations, Bugbot, Security Review)
  • Existing blocklists must migrate by June 1st

New

  • Model access controls — Admins can set allow/blocklists at model and provider level, block by speed and context window size, or block new providers/versions by default
  • Soft spend limits — Set flexible limits instead of hard caps; users get automatic alerts at 50%, 80%, and 100% of limit
  • Usage analytics filters — Break down consumption by user or product surface (clients, Cloud Agents, automations, Bugbot, Security Review)

Breaking Changes

  • Existing blocklists require migration to new model control system by June 1st — admins should visit team model settings in the Cursor dashboard immediately

Update: Changes are live now in the Cursor dashboard. Visit team model settings, spend management, and usage analytics to configure.

Source: Cursor