Troubleshooting · Zed

Zed Assistant 429 rate_limit_error — Fix

A 429 in Zed's assistant is the per-minute ceiling of the API organization behind your key. Why long threads and shared keys trigger it and what clears it.

What you see

HTTP 429
{"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your organization's rate limit of 80,000 input tokens per minute. Please reduce the prompt length or the maximum tokens requested, or try again later."}}

Why it happens

  • The per-minute token budget of the key's organization was exceeded — long assistant threads resend their whole history each message.
  • The same key is used by other tools at the same time, and their traffic shares the window.
  • Large context attachments multiply the tokens each message carries.

How to fix it

  • Wait out the minute window, then continue — a single 429 needs no configuration change.
  • Start a fresh thread for new work instead of extending one long-running conversation.
  • Give Zed its own key if the current one is shared across tools.

Related searches

  • zed claude rate limit
  • 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 API organization behind the configured key.
Why do long threads make it worse?+
Each message resends the entire thread. The counted input grows with the conversation even when your visible question is short.
Does retrying immediately help?+
No — the window is per minute. Immediate retries keep it saturated; a short pause clears it.

All Zed errors · Claude API error codes · Setup guide

Skip the broken setup

apiToken.sale serves the standard Anthropic API — same models, same SDKs, one prepaid balance. Point your tool's base URL at it, and the config on this page works as written.

Get a keyAPI docs