Proactive per-model rate limiting to prevent 429 errors
Proactive per-model rate limiting to prevent 429 errors: a task in LegoFlow-SWE (Harbor dataset). PicoClaw currently only reacts to provider rate-limit errors (HTTP 429) after they occur, using a cooldown mechanism. There is no proactive protection, so during traffic spikes or high-frequency calls…
The task
PicoClaw currently only reacts to provider rate-limit errors (HTTP 429) after they occur, using a cooldown mechanism. There is no proactive protection, so during traffic spikes or high-frequency calls the system wastes requests on 429s that could have been avoided entirely.
Part of Lego-X/LegoFlow-SWE.