Constant "200K Context" Rate Limits using personal Gemini API Key (Pro Quota Exhausted)

Support Help
, , ,
5

Hey, this is a known issue with Gemini API keys. The team is already working on a fix.

Two things:

  1. 429 error “Provider returned 429”
    Cursor is currently using a regional endpoint instead of the global one, which causes dynamic quota issues on Google’s side. Even on a paid tier, you’ll keep getting 429 errors. More details and discussion in the main thread: Gemini API key doesn't work with the latest Cursor version

  2. 200K vs 1M limit
    If you’re seeing a 200K limit, Max Mode is off. Gemini 3 Flash only gives 1M context with Max Mode enabled. Check via CMD+Shift+/ or the model selector dropdown.

Temporary workaround to reduce context size:

  • Hover over the context usage indicator to see which rules are active
  • Disable any unnecessary MCP servers (if you have them)
  • Reduce agent rules to under 300 lines

Can you share:

  • Your Cursor version (Menu > About Cursor > Copy)
  • Whether Max Mode is enabled
  • Whether you have any MCP or agent rules set up

That’ll help us understand the full picture.