# Opus 4.7 Max mode shows only 200K context instead of 1M

**URL:** <https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632>\
**Category:** Bug Reports\
**Tags:** context, max-mode, anthropic\
**Created:** [April 21, 2026, 1:52pm UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632 "2026-04-21T13:52:27Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![Georgewize](https://avatars.discourse-cdn.com/v4/letter/g/74df32/32.png) [@Georgewize](https://forum.cursor.com/u/Georgewize)\
**Post date:** [May 12, 2026, 5:07pm UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/34 "2026-05-12T17:07:35Z")

</div>

@Yasser_Elsayed @Kazopl Look here [Context decrease - Support / Bug Reports - Cursor - Community Forum](https://forum.cursor.com/t/context-decrease/160402)

---

<div class="post-metadata">

**Author:** ![Douiri\_Zayd](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@Douiri\_Zayd](https://forum.cursor.com/u/Douiri_Zayd)\
**Post date:** [May 12, 2026, 6:03pm UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/35 "2026-05-12T18:03:33Z")

</div>

It was resolved for me

![image](https://us1.discourse-cdn.com/cursor1/original/3X/c/c/cc6c61e2ef558050f3b4be91866fd96b2516f8ca.png)

---

<div class="post-metadata">

**Author:** ![Yasser\_Elsayed](https://avatars.discourse-cdn.com/v4/letter/y/65b543/32.png) [@Yasser\_Elsayed](https://forum.cursor.com/u/Yasser_Elsayed)\
**Post date:** [May 12, 2026, 6:28pm UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/36 "2026-05-12T18:28:39Z")

</div>

It was resolved for me

---

<div class="post-metadata">

**Author:** ![\_Riley](https://avatars.discourse-cdn.com/v4/letter/_/919ad9/32.png) [@\_Riley](https://forum.cursor.com/u/_Riley)\
**Post date:** [May 12, 2026, 8:05pm UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/37 "2026-05-12T20:05:17Z")

</div>

Resolved for me as well after a restart. Thanks for taking care of this quickly.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [May 13, 2026, 7:29am UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/39 "2026-05-13T07:29:50Z")

</div>

The fix for this has been deployed. The functional 300K cap that was overriding the 1M Max mode context is now resolved on our end (server-side, so no client update needed).

A few of you have already confirmed it’s working. If anyone is still seeing the old behavior, try restarting Cursor and let us know.

@Yassine_A — regarding the billing concern you raised: please email [hi@cursor.com](mailto:hi@cursor.com) with your account details so our team can look into that for you.

---

<div class="post-metadata">

**Author:** ![Santtu](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@Santtu](https://forum.cursor.com/u/Santtu)\
**Post date:** [May 28, 2026, 12:26pm UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/40 "2026-05-28T12:26:59Z")

</div>

I’m seeing this problem right now with the latest version.

Version: 3.5.38 (user setup)  
VSCode Version: 1.105.1  
Commit: 009bb5a3600dd98fe1c1f25798f767f686e14750  
Date: 2026-05-26T21:32:06.537Z  
Layout: editor  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [May 29, 2026, 9:50am UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/41 "2026-05-29T09:50:07Z")

</div>

The fix for this specific issue was deployed server-side on May 12 and has been working since then.

To help narrow down what you’re seeing, could you share a few details?

1. Which model are you using? (e.g., Opus 4.7, Opus 4.8, Sonnet 4.6)

2. Do you have Max mode enabled, and is the 1M context option selected in the model picker?

3. A screenshot of the context indicator showing the issue

4. A [Request ID](https://cursor.com/help/troubleshooting/reporting-bugs#what-is-a-request-id) from an affected chat (three-dot menu in chat \> Copy Request ID)

That will help us figure out whether this is the same issue or something different. Thanks!

---

<div class="post-metadata">

**Author:** ![Q\_F](https://avatars.discourse-cdn.com/v4/letter/q/65b543/32.png) [@Q\_F](https://forum.cursor.com/u/Q_F)\
**Post date:** [June 15, 2026, 6:37am UTC](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632/42 "2026-06-15T06:37:44Z")

</div>

Hello sir. Could you please consider supporting context limit adjust for custom models as well?

[Previous page](https://forum.cursor.com/t/opus-4-7-max-mode-shows-only-200k-context-instead-of-1m/158632.md?page=1)
