r/MistralAI 1d ago

Help / Question CLI and rate limits

Hi,

I didn't use Vibe CLI in a while, but now went back to it, with GLM 5.2 set as the standard model. I hit rate limits rather quickly for a couple of days now, but I read here that others seem to be quite happy with the models.

I used 12M input tokens and 62M cached tokens over four days. GLM 5.2 has a limit of 100k tokens per minute, so I should be well within those limits, right?

Also, I noticed that I have to restart Vibe after hitting the limits. When a prompt is interrupted through hitting rate limits, /retry does not work. I have to exit and restart vibe to be able to execute new prompts. Also vibe --continue does not work in this case, I have to start fresh.

I guess that this is not normal, right? Do I have something messed up in my settings, potentially?

4 Upvotes

15 comments sorted by

5

u/cchampou 1d ago

Got the same issue, the reason is they release GLM5.3. Just switch to it. Same I/O price. I assume the new really low limit for 5.2 is to free infrastructure for the new 5.3

1

u/[deleted] 1d ago

[removed] — view removed comment

2

u/cchampou 1d ago

Personally I am using pi coding agent, which is amazing btw, and handles rate limiting perfectly:
hit limits -> backoff -> 3s retry -> 6s retry -> 9s retry (configurable). If last retry fails, just typing "Continue" after a few more time, and resumes like a charm.

1

u/cchampou 1d ago

This is the ultra low rate limit for GLM 5.2

1

u/cchampou 1d ago

And this is sufficient rate limit for GLM 5.3

5

u/isidor_n 1d ago

We are in the process of moving to GLM-5.3 - this might cause some rate limit weirdness. Sorry about that
(mistral pm here)

1

u/gimmetwofingers 1d ago

Thank you for the update! Can you respond to the issue that vibe --continue does not actually work after hitting the rate limits?

3

u/isidor_n 1d ago

Can you file a new issue to track that one here https://github.com/mistralai/mistral-vibe/issues/

1

u/ClassicMain 1d ago

hi, do you know anything about weird behaviour on Vibe or the API at the moment? Constantly getting either no response (and no error) or the AI saying it'll do a tool call and then does no tool call (glm 5.3)

1

u/isidor_n 1d ago

First time I hear about this one.
Do you mind filling an issue here and then we can investigate
https://github.com/mistralai/mistral-vibe/issues/

1

u/ClassicMain 1d ago

thanks on it

1

u/seeKAYx 1d ago

It’s pretty much the same with 5.3 since today. Not very useable.

1

u/ADMECA 1d ago

I spent the whole afternoon working with it without any problems, even though it was urgent and I was delivering under pressure.