Max mode forced in CLI with Opus 5.5 1M

[Dustin_Pauze]

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

In Cursor CLI, when we attempt to set the model to Opus 5.5 with a 1M context window, we can set the effort level, but upon returning to the main input screen, the effort level is set to MAX.

This deviates from Cursor IDE, where we can set the model to Opus 5.5 with a 1M context window and the effort level remains set to what we intend for it to be.

Steps to Reproduce

In Cursor IDE:
Set your model to Opus 5.5, with 1M context and effort set to ‘High’. Note: upon selecting 1M Context, Max mode is enabled.

Expected Behavior

1. Cursor CLI should behave the same as Cursor IDE with model settings.
2. We should be able to use 1M context window without Max mode.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

About Cursor CLI

CLI Version 2026.09.18-9a7762b
Latest 2026.09.18-9a7762b (up to date)
Model Claude Opus 5.5 300K Medium
Subscription Tier Enterprise
OS darwin (arm64)
Terminal iterm2
Shell zsh

For AI issues: which model did you use?

Opus 5.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

[kevinn (Kevin Neilson)]

Hey @Dustin_Pauze, thanks for the report and the screenshots.

Your effort level isn’t being changed. The “MAX” is a separate Max mode label that the CLI adds after the model name. If you pick High, for example, the line under the prompt reads:

Claude Opus 5.5 1M High · MAX

• High is your effort level, and it’s what gets used.
• MAX means Max mode is on. Picking 1M context turns it on automatically, in both the CLI and the IDE.

On your team’s plan, Max mode has no effect on billing. Usage is based on the tokens you use whether it’s on or off. The IDE hides this label for plans like yours, but the CLI still shows it, which is why the two look different. This is an issue we’re tracking.

Let me know any follow-up questions!

[Dustin_Pauze]

Thank you for the clarification!