Actually i just switched to another provider that’s the point I’m trying to get across. This is not how I expect my provider to do business, I’m out
This is the tipping pint. We are out
I’m frustrated by the new requirement to use Max Mode for frontier models on legacy Team and Enterprise request-based plans.
It feels like a forced pricing and workflow change that takes away user control and makes Cursor harder to use with confidence.
Please communicate these changes more clearly and give users better control over model access and billing behavior.
And you persist that it will never be possible to use custom self-hosted models or OAuth subscriptions directly with Cursor?
Right now we are using different providers and paying 200$ per month, but this has raised code quality and speed significantly, and we save about 2500$ per month.
So, right now, with your business model, it only makes sense for us to close our subscriptions with you and migrate entirely to competitors.
If you allowed self-hosted models or OAuth login use of other model subscriptions, staying with our 25$ per seat subscription would make sense. Right now, it is just against all logic to continue our subscriptions.
You are in a competitive market. You should make your product competitive.
Feature Request: Max Mode transparency & control in CLI --print mode
As a CLI-heavy user (using cursor -p for automation), I have three concerns regarding the recent frontier model changes:
- No way to know which models are forced into Max Mode
Currently, there’s no CLI command or API to query which models will be billed as Max Mode under my plan. cursor models / --list-models only shows available models without any billing or max-mode metadata.
Request: Add a max_mode_required field to --list-models output, or provide a separate command like cursor models --show-billing so users can make informed decisions before submitting prompts.
- No --max-mode flag for --print mode
The /max-mode [on|off] slash command only works in interactive sessions. In --print mode (non-interactive), there is no way to explicitly opt out of Max Mode. Even setting “maxMode”: false in cli-config.json may be silently overridden for frontier models on legacy plans.
Request: Add a --max-mode [on|off] CLI parameter that works with --print, giving users explicit control over billing behavior in automated pipelines.
- Silent Max Mode activation is dangerous for automation
When a model is forced into Max Mode, there’s no error, warning, or confirmation — the request just runs and consumes significantly more budget. For CI/CD pipelines and batch scripting, this can lead to unexpected cost spikes.
Request: When --max-mode off is explicitly set (or cli-config.json has “maxMode”: false) but the selected model requires Max Mode, the CLI should fail with a clear error like:
Error: Model “claude-opus-4-7” requires Max Mode on your plan.
Use --max-mode on to proceed, or switch to a non-max-mode model.
This would prevent accidental budget drain and give automation users a safe default.
My cursor version:
```
Version: 3.9.16
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0
```
I have a personal legacy plan - but I am blocked from using a frontier model (including GLM-5.2) without the Max mode.
I do not mind it being auto-enabled on model switch, but the announcement originally was only for the Teams & Enterprise plans, not for the personal ones right?
Is there a workaround for this? Should I downgrade ?
Many thanks
I have a private plan, but also get this occasionally, now I seem to get this all the time. Was there a change in this for personal plans?
Same here, 4 hours ago everything was okay, but now almost every model requires MAX mode.
I also am on private and seeing the same, almost every model has this. Sadface
As @ibutab said, this should not affect the personal plans? I really hope not.
