Cursor users : Rate limit with Vertex. WTF.

Jun 4 • Tools

I was in an all-night session when i ran into the lame "we've hit our rate limit with Vertex" message.

Not only did it not complete the long running process, but Claude 4 seemed to completely lose track of the process afterwards and start the next thought process with "let me look at the codebase to see where to start". As if it had completely reset the running chat and started over.

Any Cursor users here have any advice on how to avoid this?

Is this just a Cursor problem being overloaded?

Any way to mitigate memory or chat summary failure afterwards?

I'm doing my best to always maintain docs, current_state.md, and todo lists etc, but these un-scheduled chat resets are a pain in my butt.

Maybe move back to Augment...

2 comments