Opus 4.6 Max stuck at 100% context even in brand-new chats

Support Bug Reports
, , ,
1

Describe the Bug

I’m seeing a bug with Opus 4.6 Max where the context meter is constantly stuck at 100% used.

This happens even after restarting Cursor and creating a completely brand-new chat. The moment the new chat opens, it already shows 100% context used, even with only a tiny amount of text in the conversation.

It also seems to start summarizing the chat context almost immediately, which makes the model basically unusable.

Has anyone else seen this with Opus 4.6 Max?

Steps to Reproduce

Try using any of the Opus 4.6 models within Cursor

Expected Behavior

The context is not being 100% used the moment you interact with it.

Operating System

MacOS

Version Information

Cursor version 3.0

For AI issues: which model did you use?

Opus 4.6

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, this is a known bug. On the Opus 4.6/4.7 backend in Max mode, the context gets clamped to 200K instead of 1M. That’s why the context ring immediately shows 100% and triggers early summarization. We’re tracking the issue. I can’t share an exact ETA yet, but I’ll post an update in the thread as soon as we have a fix.

Similar reports for context:

As a temporary workaround, you can switch to Sonnet 4.6 in Max mode, or use Opus without Max until we fix the clamping.

7

Okay, great. Please let me know once it’s fixed.

By the way, it’s not just in max mode; it’s also opus 4.6 thinking non-max mode

11

Hey @G4Q4

This should be fixed now, please have another look!

If for some reason it’s not fixed, please share the Request ID of an affected chat!

13

Nope. The bug is still very much alive and well.

Just from asking it to commit the edits in my source control, it’s had to summarise three times.

8ccda576-bb39-4c78-a256-96e21c152899

14

Hey @G4Q4!

Had a look – and your case is different from the other bug mentioned.

Here, you have some MCP servers whose tool descriptions are taking up an insane number of tokens (almost the entire context window).

The fix is to disable or trim down MCP servers you’re not actively using. You can do this in Cursor Settings > MCP. That should free up the bulk of your context for actual work.

15

Yes, that fixed it! the bloody post-hog and century MCPs. That’s crazy. Thank you so much.