Hi, from what I understand, Cursor limits the context window to 10k or 20k tokens (what’s the actual value?) regardless of the model used. I get that this is to manage costs of subscription users. But any chance you could at least allow us to configure this limit when using an API key instead of subscription allowances, since we’d be paying for it ourselves then and it incurs no cost to Cursor (even saves costs because every request per API key is one less request that Cursor has to pay for, or several if the context limit is causing repeated issues as it often does). And I’d really like to be able to make use of that juicy 128k context window when needed. Of course this does mean Cursor would need be made to actually use the extra space up to the configured limit. Thanks.
3 Likes