← All fixes
429Cline· Rate limits

Cline “API Request Failed” 429 — how to fix

API Request Failed — 429 status code
Quick answer

Cline itself has no limits — the 429 comes from whichever provider your key belongs to (OpenAI, Anthropic, OpenRouter…). Cline's agent loop just hits provider rate limits faster than chat would. Fix the provider, or switch Cline to one without per-minute caps.

What causes it

How to fix it

  1. Add/raise the retry delay in Cline's provider settings so bursts spread out.
  2. Move up a usage tier with your provider, or request higher limits.
  3. Use a provider without per-minute caps for agent work.
  4. Point Cline's “OpenAI Compatible” provider at a flat-rate endpoint — one settings change.
Running an agent?

A single Cline task can be 20–50 requests. Providers size RPM limits for humans typing, not agent loops — that mismatch is the whole problem.

The permanent fix

Stop hitting this entirely

Cline speaks to any OpenAI-compatible endpoint: set provider to OpenAI Compatible, base URL https://api.stdcmpt.com/v1, model standardcompute — no per-minute request cap, flat monthly price, and under sustained load requests batch gracefully instead of 429ing mid-task. Guide: /integrations/cline.

Get a free API key →How it connects →

FAQ

Is the 429 Cline's fault?

No — Cline is BYO-key, so limits are always the provider's. The same key hits the same limits in any tool; agents just get there faster.

Related errors

429 Too Many Requests — what it means & how to fixAny provider · 429OpenAI “Rate limit reached for requests” (429)OpenAI · 429Why your AI agent keeps getting rate limited (and how to stop it)Any agent