Claude Code / AI Coding Tools

Anthropic API rate limit reached despite low session/weekly usage in Claude Code

User blocked by undocumented per-minute rate limits in Claude Code despite low overall usage; needs workaround or per-minute limit documentation Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 20, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs)
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: May 20, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs) is a Claude Code failure pattern reported for developers trying to user blocked by undocumented per-minute rate limits in claude code despite low overall usage; needs workaround or per-minute limit documentation. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #39948 on anthropics/claude-code — user processing 148 PDFs hits rate limit at 6% session / 29% weekly usage, waited 3+ hours with no resolution. No short-term per-minute limit docs exist. High commercial value: Claude Code Pro/Pro+ subscription broken for paying users. Category: AI Coding Tools (Claude Code).

Common causes

GitHub issue #39948 on anthropics/claude-code — user processing 148 PDFs hits rate limit at 6% session / 29% weekly usage, waited 3+ hours with no resolution. No short-term per-minute limit docs exist. High commercial value: Claude Code Pro/Pro+ subscription broken for paying users. Category: AI Coding Tools (Claude Code).

Quick fixes

Confirm the exact error signature matches API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs).
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs) exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs) mean in Claude Code?

API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs) indicates the workflow described by "Anthropic API rate limit reached despite low session/weekly usage in Claude Code" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs)?

Check whether this cause matches your environment: GitHub issue #39948 on anthropics/claude-code — user processing 148 PDFs hits rate limit at 6% session / 29% weekly usage, waited 3+ hours with no resolution. No short-term per-minute limit docs exist. High commercial value: Claude Code Pro/Pro+ subscription broken for paying users. Category: AI Coding Tools (Claude Code).

Is the API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs) guidance source-backed?

The "Anthropic API rate limit reached despite low session/weekly usage in Claude Code" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs)?

For "Anthropic API rate limit reached despite low session/weekly usage in Claude Code", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging API Error: Rate limit reached (session usage 6%, weekly 29%, no per-minute docs)?

For "Anthropic API rate limit reached despite low session/weekly usage in Claude Code", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.