Even small requests (<200K tokens) are billed and throttled under the long-context tier.
This appears to have been introduced recently, as older requests used the 200K mode without the beta flag.
While having access to the 1M context window is a much welcome feature, it should be on-demand and invoked only with user consent.
Enabling it automatically makes the product effectively unusable for AWS Bedrock users due to the higher cost and much stricter service quotas associated with the long-context mode.
Requests:
Confirm whether this behavior is intentional.
Add a setting or environment variable to disable long-context mode.
Make the 1M context window available only on user opt-in, not by default.
Steps to Reproduce
Open Cursor IDE and select Claude Sonnet 4.5 as the model (via AWS Bedrock key).
Send any prompt - it can be small, e.g. 1+1= (see screenshot)
Check your AWS CloudWatch logs for the corresponding InvokeModelWithResponseStream event.
Observe that the request payload includes:
"anthropic_beta": ["context-1m-2025-08-07"]
Note that the same request is billed under Claude Sonnet 4.5 – Long Context pricing and is subject to stricter rate limits, even though the input is below 200K tokens.
Expected Behavior
Cursor should default to 200K context mode unless the user explicitly choses to enable the 1M context mode.
For AI issues: add Request ID with privacy disabled
Request ID: 8d740de6-b688-4c4a-b652-1769519fa073
Error:
ERROR_OPENAI_RATE_LIMIT_EXCEEDED
Hit your Anthropic API key rate limit.
You're using your own API key, and we received a rate limit error from Anthropic.
Severity: High - this behavior is leading to substantial unexpected billing (hundreds of dollars per day) and makes Cursor unusable under AWS Bedrock quotas for the 1M context model.
I switched to Claude Sonnet 4, and it seems to have the same issue (see screenshot). I also verified it in AWS CloudWatch, where the request payload includes:
"anthropic_beta": [
"context-1m-2025-08-07"
]
So the 1M context mode is being enabled automatically for Sonnet 4 as well.
For context, we have special pricing and AWS credits tied to Bedrock usage, so switching to the direct Anthropic API isn’t a viable workaround.
The main issue is quota: the 1M context mode is still in BETA with only 2 RPM vs 200 RPM for the standard mode - a 100x reduction that’s causing immediate rate limits.
We’ve requested a service quota increase from AWS for the 1M mode as a temporary workaround, but approvals typically take a couple of weeks - leaving us unable to use Cursor.
In the meantime, I am looking for a way to intercept and strip the anthropic_beta header from Bedrock API requests (either via API Gateway proxy or local request interception) if you know if this would work or have any workaround please let me know - ideally though this gets sorted quickly.
Hi, following up on the Bedrock integration issue. It’s been six days and Cursor remains effectively unusable. Every request hits Bedrock rate limits, and our cost has more than doubled since the 1M context mode started being enabled automatically.
Could you please confirm whether a fix is planned within the next few days? We need to decide whether to invest time in evaluating other IDE setups.
As mentioned, the issue is caused by the automatic inclusion of the Max Mode flag in Bedrock requests, even when Max is not toggled on:
"anthropic_beta": ["context-1m-2025-08-07"]
Please remove this flag, or make the 1M context mode user-selectable (for example, only when “Max Mode” is enabled).
The team is aware of the issue but currently working on higher priority items. They will review this when bandwidth allows, though I can’t provide a specific timeline at this point.
In a recent release, they addressed the UI inconsistencies. Selecting MAX mode now correctly shows 1M tokens, and otherwise 200k. However, this is purely a UI change, which amplifies the issue since Cursor will still invoke the 1M model regardless.
It’s a shame Bedrock was once supported by Cursor and now it’s not. @Cursor: You should consider updating your documentation since it’s incorrect and comes with hidden costs.
If you’re someone who’s affected by this or similar issues, DM me.
@deanrie It seems like you are willfully deceiving your customers by claiming to support Bedrock - yet there have been zero updates in your documentation regarding hidden charges or the fact that only 1M context is supported. Things were working fine two months ago - it’s literally just a simple flag that gets inserted. No excuses, just a really disappointing company.
Do you guys understand that it has been over two months that you don’t support Sonnet 4 and 4.5 via Bedrock (like not accessible at all). Is there anyone there who cares to fix it?
