Enterprise Account: All Agent Requests Incorrectly Blocked as "Max Mode Disabled" Can Not Use *Any* Model

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor Agent is completely unusable on my work Team account. Every Agent request fails immediately with the following error:

Max mode has been disabled for your team. Please contact your team admin for more information.

This occurs even when I explicitly select a model that should not require Max Mode, including Composer 2.5, and submit a trivial prompt.

I am not running in Max Mode. Max Mode is not selected, and no Max Mode option is visible in the Agent model dropdown. The error therefore appears to be incorrectly applied to all Agent requests rather than only to requests that actually use Max Mode.

Steps to Reproduce

Open Cursor 3.12.20 while authenticated with the affected work Team account.
Open Agent in a new conversation.
Open the model dropdown.
Explicitly select Composer 2.5.
Confirm that Max Mode is not selected and that no Max Mode option is visible.
Enter the following trivial prompt:
Output a simple response: Test acknowledged.
Submit the request.

Actual Result

The request is rejected immediately with:

Max mode has been disabled for your team. Please contact your team admin for more information.

No model response is generated.

The same error occurs for all attempted Agent requests, not merely for frontier models or requests using a large context window.

The error also occurs for every other model available, including Gemini 3.5 Flash.

Expected Behavior

Because Composer 2 was explicitly selected and Max Mode was neither selected nor available in the UI, Cursor should process the request normally using Composer 2.5.

At minimum, disabling Max Mode at the team level should block only model configurations that actually require Max Mode. It should not prevent all Agent use.

Screenshots / Screen Recordings

Screenshot 2026-07-22 144339.png
Screenshot 2026-07-22 144339.png1277×794 34.1 KB
Screenshot 2026-07-22 144444.png
Screenshot 2026-07-22 144444.png1273×796 37.7 KB

Operating System

Windows 10/11

Version Information

Version: 3.12.30 (user setup)
VS Code Extension API: 1.128.0
Commit: 63a2996a10d9e476b6c28e951dd7691d9c0cf480
Date: 2026-07-21T22:50:03.568Z
Layout: IDE
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: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 2.5, Gemini 3.5 Flash, Grok 4.5, ChatGPT 5.6 Sol

For AI issues: add Request ID with privacy disabled

Request ID: 93817648-c0bd-47cf-b5b3-d4f036462ded
Max mode disabled Max mode has been disabled for your team. Please contact your team admin for more information.
ActionRequiredError: Max mode disabled Max mode has been disabled for your team. Please contact your team admin for more information.
at UIf (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9292:6260)
at hZi (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9292:5411)
at Cxp (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9293:11972)
at Object.classify (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9293:16501)
at HIf (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9293:5856)
at async HYo.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9293:15853)
at async XH.runAgentLoop (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15878:72694)
at async IEa.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15906:14489)
at async IEa.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15906:24315)
at async eDe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/brian.smith/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9476:2491)

Additional Information

This error began after updating to 3.12.30. As an enterprise account, I can not update to a more recent release.

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi Brian, thanks for the thorough report. The request IDs, version info, and screenshots made this quick to confirm on our side.

You’re right that this isn’t correct behavior, and your setup is fine. Here’s what’s happening: your team has Max Mode disabled at the team level, and we’ve confirmed a bug where Agent requests can still carry a leftover Max Mode setting even when you’ve selected a model that doesn’t use it, like Composer 2.5. A recent update also removed the Max Mode toggle from the model picker, so there’s no way for you to see or clear that setting yourself. The result is that every Agent request from your account gets incorrectly rejected, which matches exactly what you described.

I verified this with the request IDs you shared: the request arrived on our servers flagged as a Max Mode request even though you had Composer 2.5 selected, and that flag is what triggered the block.

In the meantime, using Auto for model selection works normally and isn’t affected by this, so that’s the best workaround until the fix lands. No downgrade or settings changes needed on your end.

We’re tracking this internally and working on a fix. I’ll follow up on this thread as soon as there’s an update.

8

Thank you so much for the quick response!

For others facing the same issue, I’ve also established that rolling back to 3.12.10 an making use of the Max mode toggle works.

9

Is there an issue tracker ID I could use to follow the progress of this? I’m having the same issue and do not have the option of restoring an older version of the app. Thanks!

10

Hi @Dan_Johnson By commenting on this post as you’ve done this will allow us to notify you when we have any updates on this! It should show as unread in notifications and you should also get an email along the lines of something like “Cursor community forum: Someone replied to your post”

We’ll keep you updated with any progress on this

11

As an update which might help troubleshooting: I selected Composer 2.5 for a prompt and was rejected with the same “max mode disabled” message. When I reopened the model selection UI I saw that the max mode toggle was enabled (which I had not done). Turning it off and resubmitting my prompt for Composer 2.5 worked correctly. I was then able to switch to other models.

My enterprise account admin has temporarily enabled max mode for me, but it wasn’t until I saw this Composer-specific toggle (as opposed to the max effort options when using “edit” for another lab’s model) that I was able to resume choosing model manually, as well as using subagents which were also previously erroring.

14

Hi @here This is now fixed! Agent requests from your account were being sent with a Max Mode flag still attached that you had no way to see or clear, and we’ve made a change on our side so those requests are no longer blocked. Nothing to update on your end: any model should work normally again, and neither the 3.12.10 rollback nor staying on Auto is needed anymore. Lmk any follow-ups!