Feature request for product/service
AI Models
Describe the request
Feature Request: Account-Level Model Restrictions (Disable Specific Models and High/Fast Variants)
I’d like to request an account-level feature that allows users to explicitly disable specific models and their variants (such as High/Fast) across the entire Cursor account.
Problem
Currently, Cursor may automatically switch to a different model or a more expensive variant, even when a specific model has been selected.
This is especially problematic when using subagents. Even if a subagent is explicitly instructed to use a particular model, Cursor sometimes ignores that instruction and launches a different model or a more expensive variant instead.
As a result:
- usage becomes unpredictable;
- token/cost control is lost;
- carefully configured workflows become unreliable;
- users cannot guarantee that automation stays within their intended budget.
Proposed Solution
Introduce an Account-Level Model Restrictions page where users can:
- Disable specific models completely.
- Disable High/Fast variants independently.
- Allow only a selected whitelist of models.
- Reject any request that attempts to use a disabled model instead of silently switching to another one.
For example, if a subagent (or any Cursor feature) tries to use a disabled model, Cursor should return an error such as:
“This model is disabled by your account policy.”
rather than automatically falling back to another model.
Why this matters
Many users optimize their workflows around specific models based on quality, latency, context size, or cost.
Automatic model switching makes behavior unpredictable and can significantly increase usage costs without the user realizing it.
An account-level policy would provide deterministic behavior, improve cost control, and make subagents and automation much more reliable.
I believe this would be particularly valuable for power users, teams, and anyone running automated workflows where predictable model selection is essential.