Rank, 14 days: 3 on the Cursor sheet
2 people reported

All time, since Oct 29.

BYOK Gemini rate limit errors

“I'm using my own Google key and I often run into API rate limit errors despite having enough headroom on my Google account.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/cursor/issues/23018/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Rate limit errors with own Google API key despite headroom. Using a custom Google key, rate limit errors appear in chat while direct Gemini calls with the same key succeed and usage is within limits.

Is this your bug?

File my report
Where
Cursor IDE
Versions
3.27.22 to 3.28.7
Platforms
macOS, Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Gemini provider 401 error2 people

Original reports2, newest first

  1. Gemini 4 Argon model rate limit on Cursor#177667
  2. BYOK incorrectly throws API rate limits errors#176695

Do you work on Cursor?

Claim its RAP Sheet to see what your users report and answer them in one place.