#Claude Code Auth Key 429
1 messages · Page 1 of 1 (latest)
429 isn’t an “auth key is bad” signal — it’s rate limiting / quota / overload. The reason it can work on one computer but not the other is usually one of these:
-
Different network / IP
Office/VPN/VPS/datacenter egress IPs can get throttled much more aggressively than a home connection.
Quick test: try the “broken” machine on a phone hotspot (no VPN). If it suddenly works, it’s the network/IP/proxy. -
Different credentials are actually being used
Claude Code has multiple auth paths (Claude Teams/Enterprise, Console API key, Bedrock/Vertex/etc) and it also supportsapiKeyHelperin settings; settings can be managed at/etc/claude-code/on Linux/WSL. So one machine may be using a different key/org than you think. -
You’re hitting token/request limits on that machine because it’s doing more work
Claude Code can generate a lot of requests (repo scanning, big context, parallel calls). That can trip tokens-per-minute limits even if “normal prompts” work elsewhere.
If you paste the exact 429 error text (redact the key; keep the message + any request id), I can tell which bucket it is. Also: what environment is failing (OS, home vs office/VPN, local vs VPS)?
If you want a fast self-check: from the failing machine run a single tiny API call (using your env var key) and see if it still 429s immediately — that distinguishes “API/account limit” vs “Claude Code usage pattern / concurrency / repo size”.
HTTP 429: rate_limit_error: This request would exceed your account's rate limit. Please try again later. (request_id: req_011CY9VqAPWX9iMqDzVUSyta)
That specific message means Claude Code did authenticate, but Anthropic rejected the call because it would exceed your org/account API rate limits (TPM/RPM / spend-tier limits). It’s not a “bad key” error.
Why it can work on one computer but not the other usually comes down to one of these:
- They’re not actually using the same auth/account
- One machine might be using a different API key / different Anthropic org, or even a different auth method (Claude Teams/Enterprise vs Console API key).
- Easiest check: confirm the two machines are using the same key (compare last 4 chars locally; don’t paste it here).
- The failing machine is sending a much bigger request
- Big repo context / lots of files / multiple concurrent requests can exceed your per‑minute token budget even if “normal prompts” work elsewhere.
- Quick test: run Claude Code in an empty/small folder and ask something tiny.
- If that works → it’s repo size / context / concurrency.
- If that still 429s immediately → it’s truly your account/org limit.
- Something else is burning the limit in the background
- Another Claude Code session, CI job, editor plugin, etc. using the same key can push you over.