Troubleshooting · Zed

Zed Assistant 429 rate_limit_error — Fix

A 429 in Zed's assistant is the rate or concurrency ceiling of the account behind your key. Why agent threads and shared keys trigger it and what clears it.

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

  • The rate or concurrency ceiling of the key's account was exceeded — agent threads send several requests in quick succession.
  • The same key is used by other tools at the same time, and their traffic shares the ceiling.
  • Retries during a saturated window keep it saturated.

How to fix it

  • Wait for the Retry-After interval, then continue — a single 429 needs no configuration change.
  • Run fewer assistant threads at the same time on one key.
  • Pause other tools that share the key during long runs.

Related searches

  • zed assistant 429

FAQ

Is this Zed's limit or my key's limit?+
The key's. Zed adds no metering of its own; the 429 comes from the account behind the configured key.
Why do agent threads make it worse?+
An agent thread sends a request for every step, often back to back. The request rate grows with the work even when your visible question is short.
Does retrying immediately help?+
No — immediate retries keep the window saturated; a short pause clears it.

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.