Troubleshooting · Cline

Cline 429 rate_limit_error — Stop the Retry Loop

Cline agent runs send requests back to back and then loop on 429 retries. Why agent workloads reach the account's rate ceiling and how to get a run through.

What you see

HTTP 429
{"error":{"message":"Rate limit reached. Please retry shortly.","type":"rate_limit_error","param":null,"code":"rate_limit_exceeded"}}

Why it happens

  • Agent loops send one request per step, back to back, so a single active task can reach the account's rate ceiling alone.
  • The key is shared with other tools or teammates and their traffic counts against the same ceiling.
  • Automatic retries during a saturated window keep the window saturated.

How to fix it

  • Let one 429 pass — Cline backs off and retries. If a run loops on 429s, pause it for a minute instead of restarting it repeatedly.
  • Run one Cline task per key at a time, and pause other tools that share the key during a long run.
  • If you consistently need more throughput, raise the ceiling with the key's issuer rather than fighting it with retries.

Related searches

  • cline 429 rate limit
  • cline retrying request

FAQ

Why does Cline hit 429 so much faster than chat tools?+
An agent step is not one message — every iteration is a new request with the history, file context and tool output. Its request rate is several times a chat's.
Will retrying immediately help?+
No — immediate retries keep the window full. Backing off for the Retry-After interval is what clears it.
Is this Cline's own limit?+
No. Cline has no metering of its own with your key; the 429 is the ceiling of the account behind that key.

Skip the broken setup

apiToken.sale serves GPT and Gemini models through OpenAI-compatible, Messages (Anthropic format) and native Gemini endpoints — standard SDKs, one key, one prepaid balance. Point your tool's base URL at it, and the config on this page works as written.