# Max mode vs non-max mode (context max, not thinking max) **URL:** \ **Category:** Feedback\ **Tags:** max-mode\ **Created:** [March 10, 2026, 1:10am UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215 "2026-03-10T01:10:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![charles](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@charles](https://forum.cursor.com/u/charles)\ **Post date:** [March 10, 2026, 1:10am UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/1 "2026-03-10T01:10:59Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug According to the AI support bot that running in max context mode, even when under the max context window (E.g. the first 200k) the token cost is 1.2x instead of 1.0. Shouldnt the “max” mode not incur any charges until you exceed the normal token amount? seems very strange there would be an extra cost for the same thing unused? ### Steps to Reproduce Run max mode in a new window, see higher per-token costs. ### Expected Behavior Costs are identical between max and non-max until exceeding the 200k base token window (Anthropic for example) ### Operating System MacOS ### Version Information Version: 2.6.14 VSCode Version: 1.105.1 Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080 Date: 2026-03-08T15:36:54.709Z Build Type: Stable Release Track: Early Access Electron: 39.6.0 Chromium: 142.0.7444.265 Node.js: 22.22.0 V8: 14.2.231.22-electron.0 OS: Darwin arm64 24.6.0 ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [March 10, 2026, 8:40am UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/4 "2026-03-10T08:40:15Z")
Hey, this is expected behavior. Max Mode always applies a 1.2x multiplier to the API cost, no matter how much context is actually used in the conversation. From the docs: [Max Mode | Cursor Docs](https://cursor.com/help/ai-features/max-mode) > Max Mode consumes usage at 1.2x the normal API rate for the selected model. The 1.2x is the fee for access to Max Mode features like extended context, subagents with models other than Composer-1, and image generation on request-based plans, not for actually going over the base context window. If you are not using subagents or image generation, it is usually easier to keep Max Mode off. Colin explains it in detail here: [Claude opus 4.5: Max vs Default mode - #3 by Colin](https://forum.cursor.com/t/claude-opus-4-5-max-vs-default-mode/150050/3) ---
**Author:** ![charles](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@charles](https://forum.cursor.com/u/charles)\ **Post date:** [March 10, 2026, 9:36am UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/5 "2026-03-10T09:36:36Z")
Hi Dean, thats really not very transparent, it should be called out in the text/on the pricing page. Also, it seems pretty crazy. Happy to pay for extended context, when using it, but not int he run up. Claude does not charge for this, neither should Cursor. Actually it’s a double hit because you charge 20% for max mode and another 20% on top of that for the token fee or whatever it is. If you can share disgruntlement with your product team it would be appreciated. Also, gotta rename one of the max’s. Its confusing as hell. Max thinking, max context. Pick max for one, use extended for the other or something. ---
**Author:** ![charles](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@charles](https://forum.cursor.com/u/charles)\ **Post date:** [March 10, 2026, 9:47am UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/7 "2026-03-10T09:47:11Z")
From the pricing page: —- [Max Mode](https://cursor.com/docs/models-and-pricing#max-mode) Max Mode extends the context window to the maximum a model supports. More context gives models deeper understanding of your codebase, leading to better results on complex tasks. The models table above shows each model’s maximum context size. Max Mode uses token-based pricing at the model’s API rate, so it consumes usage faster than the default context window. On individual plans, a 20% upcharge is added to the model’s API rate. On [Teams and Enterprise plans](https://cursor.com/docs/account/teams/pricing), the [Cursor Token Fee](https://cursor.com/docs/account/teams/pricing#cursor-token-fee) applies instead of the 20% upcharge. — It’s not accurate since the model API rate is not increased until you exceed 200k tokens. There is a hidden 20% here. It should be just the token rate on top of the base model rate. But thats not what appears to be happening. e.g. from the usage dashboard there are 4 variants: ![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/8/78f33b6a493dd593da63ec53aedf8257f0bd035e.png) If you can decode this, that would be amazing. These all vary ontop of the token access fees that are separate line items. Very confusing. ---
**Author:** ![Luis\_B](https://avatars.discourse-cdn.com/v4/letter/l/bc79bd/32.png) [@Luis\_B](https://forum.cursor.com/u/Luis_B)\ **Post date:** [March 24, 2026, 7:35am UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/8 "2026-03-24T07:35:55Z")
I Agree with @charles . Max Mode is not transparent enough and the upcharge of 20% for using Max Mode even when **not** going **above** the **normal context window size** (e.g. 200K) is ridiculous. **Max Mode should be integrated automatically and trigger when the context window gets too big**. That makes sense and would be fair. ---
**Author:** ![charles](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@charles](https://forum.cursor.com/u/charles)\ **Post date:** [April 2, 2026, 7:29pm UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/9 "2026-04-02T19:29:53Z")
Sadly after spending tens of thousands on Cursor, I’ve had to abandon it for claude code. Results are typically better, and actual spend cost is 1/4. Sorry folks, great product, but not manageable pricing models. At the end of the day, there’s not enough value add over the other tools to warrant using Cursor anymore. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [April 24, 2026, 7:30pm UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/11 "2026-04-24T19:30:20Z")
Closed on April 24, 2026, 7:30pm UTC This topic was automatically closed 22 days after the last reply. New replies are no longer allowed. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [April 27, 2026, 1:41pm UTC](https://forum.cursor.com/t/max-mode-vs-non-max-mode-context-max-not-thinking-max/154215/12 "2026-04-27T13:41:22Z")
Quick update to share here! > [@Opus 4.7 context window (increase non-max above 200k)](https://forum.cursor.com/t/opus-4-7-context-window-increase-non-max-above-200k/158527/5): > > Hey there @zebra ! Good news – for users on individual token-based plans, there is no longer a 20% markup for using Max Mode. Hope this helps!