Admins can now manage allow/block lists at the model and provider level, set soft spend limits, and get usage alerts at multiple thresholds. Cursor also expanded the analytics view so teams can break usage down by user and product surface.
This is the kind of release that matters once AI usage moves beyond hobbyist scale. It helps organizations keep experimentation alive while limiting surprise spend and reducing admin friction.
Enterprise teams should migrate existing blocklists before the June 1 deadline mentioned in the post. If you're managing Cursor in a larger org, set soft limits first and use the analytics views to find where usage is actually going.
Read Original Post →