Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Cline error

Cline: 429 ... Number of request tokens has exceeded your per-minute rate limit

Error message
429 {"type":"error","error":{"type":"rate_limit_error","message":"Number of request tokens has exceeded your per-minute rate limit (https://docs.anthropic.com/en/api/rate-limits); see the response headers for current usage. Please reduce the prompt length or the maximum tokens requested, or try again later. You may also contact sales at https://www.anthropic.com/contact-sales to discuss your options for a rate limit increase."}}

Status: WorkaroundLast verified 3 documented fixes5 sources

What it means

The model provider rejected the request because your account exceeded its per-minute request or token rate limit. Cline forwards the provider's 429.

Causes

  • Provider account tier limits; a Cline contributor stated rate limit errors are almost always caused by the provider you use and each provider has its own limits.
  • Large prompts per request (system prompt plus file context) consuming the per-minute token allowance.

How to fix it

  1. Fix 1.

    Update Cline: PR #1605 added retry handling for 429 errors using response-header timing with exponential backoff (3.3.0: "Add automatic retry for rate limited requests").

  2. Fix 2.

    Raise your provider account tier or contact the provider; or use a routing provider such as the Cline provider, which a contributor said has high rate limits with upstream providers.

  3. Fix 3.

    Cline API docs: for 429 Too Many Requests, wait and retry with exponential backoff, add delays between requests, and reduce concurrent requests.

More Cline errors

All 17 Cline errors

FAQ

What does "429 ... Number of request tokens has exceeded your per-minute rate limit" mean in Cline?

The model provider rejected the request because your account exceeded its per-minute request or token rate limit. Cline forwards the provider's 429.

How do I fix "429 ... Number of request tokens has exceeded your per-minute rate limit"?

There are 3 documented fixes. Start with the first: Update Cline: PR #1605 added retry handling for 429 errors using response-header timing with exponential backoff (3.3.0: "Add automatic retry for rate limited requests").

Is this Cline error fixed?

Status: Workaround. No release removes the cause. The documented fixes work around it. Affected versions: All versions; automatic retry since 3.3.0

Sources

Last verified against 5 sources: official docs, maintainer replies and release notes.

Newsletter

Fixes for the tools you use, weekly

One email per week. New coding agent releases, what broke, and how developers are working around it.