Cursor adds enterprise model controls, soft spend limits, and richer usage analytics
Cursor’s May 4, 2026 update adds granular model/provider access controls for Enterprise admins, introduces soft spend limits with automated alerts, and expands usage analytics so admins can break consumption down by product surface (including Cloud Agents, Bugbot, and Security Review).
Cursor shipped a set of updates aimed at Enterprise admins: more granular model access controls, softer spend management, and more detailed usage analytics. (Cursor changelog (May 4, 2026))
What’s new
Model access controls (providers, models, and configurations)
Admins can now set allowlists/blocklists at both the provider and model level, including the ability to block entire providers or specific model configurations (for example, based on speed or context window size). (Cursor changelog (May 4, 2026))
Enterprises can also choose to block new providers or model versions by default. (Cursor changelog (May 4, 2026))
If your org already uses blocklists, Cursor says you’ll need to migrate to the new system by June 1. (Cursor changelog (May 4, 2026))
Soft spend limits + automated usage alerts
Instead of hard limits that block users, admins can set soft limits and receive automated alerts as users approach their thresholds (50%, 80%, and 100% of either soft or hard limits). (Cursor changelog (May 4, 2026))
Usage analytics by user and product surface
The usage analytics tab now supports filtering by individual users and breaking usage down by product surface. Cursor lists these surfaces as:
- clients
Cloud Agents- automations
BugbotSecurity Review
(Cursor changelog (May 4, 2026))
Where to find it
Cursor points admins to the team model settings, spend management settings, and usage analytics tab in the Cursor dashboard. (Cursor changelog (May 4, 2026))
Frequently Asked Questions
What did Cursor change for Enterprise admins in this update?
Cursor introduced a new system for model access controls, updated spend management with soft limits and alerts, and added more detailed usage analytics filtering and breakdowns.
What’s the deadline for migrating existing model blocklists?
Cursor says customers with existing blocklists need to migrate to the new model controls system by June 1.
What product surfaces can usage analytics be broken down by?
Cursor lists clients, Cloud Agents, automations, Bugbot, and Security Review as the product surfaces available in the updated usage analytics breakdown.