The "Whole 200k Context Window" of Claude 3.7 Sonnet Max

@Taidan @normalnormie @T1000
This info might help y’all understand what’s going on. Also, kindly asking everyone to keep it friendly.
Regarding costs - I get what Anthropic charges for tokens. Whether it’s $0.05, $0.15 or $0.5 per request, I’m cool with paying. Token-based pricing? That works for me too.
What I’m pointing out is Cursor literally BLOCKS any input exceeding ~70K tokens. Anyone can verify this by checking network traffic - you’ll see that “HTTP 500” error coming back.
For folks talking about “input+output=total context window” - let me clarify. I used the simple “Ask” function with one basic request: tell me the first sentence of my text. Can’t see how that would use tons of output tokens.
Not trying to start drama with this post. Just looking for Cursor to explain what “Whole 200k Context Window” actually means because the current implementation doesn’t match the marketing.
Cursor seems to be declining in quality - questionable models, reduced context windows, even with pay-per-request models. I’m curious - anyone can give me an answer------what’s the actual context window size for Pro plan’s “Claude-3.7-sonnet”? That version just ignores parts of your context instead of refusing answers, making it hard to test. Haven’t found a solid Cursor alternative yet, but open to suggestions if anyone has them.

3 Likes

I can suggest why this happens without having internal knowloadge, @deanrie can clarify this point with an official response, from my understanding 70k is a “safe” limit for Cursor, Cursor doesn’t know or calculates a possible output context based on your prompt and I agree with you it can be optimized.

1 Like

So much for A.I! Complete misnomer.
It is ultimately just building a huge wall around human creativity!

1 Like

from my understanding 70k is a “safe” limit for Cursor

Interesting that you seem to have a better understanding than the cursor devs who’ve increased the limits to 120k for non max (Cursor – Models)

I can suggest

Nah, probably better that you don’t, respectfully.

Most of this is irrelevant due to:

  • Updated documentation
  • We all likely understand that Cursor can not use complete context in first request as it has to have space for follow up requests, tool calls, etc…
1 Like

No idea what you’re talking about. Cursor increased the context window, presumably they leave some of it for other stuff.

Yeah thats what i wrote