Bug: Rate limit triggered despite 0% usage in /usage
Status Fixed / completed
Reported on v2.1.81
Maintainer reply None cached
Activity 5 comments · opened Apr 2, 2026 · closed Apr 2, 2026
Rate limit triggered despite 0% usage in /usage**
Plan: Max (20x)
- Sent a message in Claude Code → got rate limit error ("resets 6pm Australia/Hobart")
- Ran /usage immediately after → Current session: 0% used, Sonnet only: 0% used, Weekly: 22% used
- Reset time in error (6pm) doesn't match /usage (8pm) — 2hr discrepancy
/usage and the actual rate limit are clearly out of sync.
Environment Info
- Platform: darwin
- Terminal: vscode
- Version: 2.1.81
- Feedback ID: 654ed7b5-5f6a-4a4b-a69e-31173c678b7a
<img width="545" height="446" alt="Image" src="https://github.com/user-attachments/assets/9c46e1fc-358b-4d05-94dd-2ce0e2e62df0" />
This is blocking my work entirely. As a Max plan subscriber, being unable to use the tool I'm paying for — with no indication of why in the usage stats — is unacceptable. Please investigate urgently.
Errors
[{"error":"MaxFileReadTokenExceededError: File content (17809 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at gT9 (/$bunfs/root/src/entrypoints/cli.js:4312:23670)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T03:57:59.187Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/m/Dev/AI/edge-protocol.\n at call (/$bunfs/root/src/entrypoints/cli.js:4321:6398)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T03:58:51.072Z"},{"error":"Error: LSP server plugin:typescript-lsp:typescript failed to start: Executable not found in $PATH: \"typescript-language-server\"\n at start (/$bunfs/root/src/entrypoints/cli.js:3133:22278)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:03:59.141Z"},{"error":"Error: Executable not found in $PATH: \"typescript-language-server\"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at start (/$bunfs/root/src/entrypoints/cli.js:3133:20831)\n at A (/$bunfs/root/src/entrypoints/cli.js:3133:24600)\n at O (/$bunfs/root/src/entrypoints/cli.js:3133:33741)\n at j (/$bunfs/root/src/entrypoints/cli.js:3133:34078)\n at z (/$bunfs/root/src/entrypoints/cli.js:3133:34628)\n at call (/$bunfs/root/src/entrypoints/cli.js:3161:1270)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:03:59.141Z"},{"error":"Error: Failed to start LSP server for file /Users/m/Dev/AI/edge-protocol/src/commands/list-episodes.ts: Executable not found in $PATH: \"typescript-language-server\"\n at O (/$bunfs/root/src/entrypoints/cli.js:3133:33767)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:03:59.141Z"},{"error":"Error: Executable not found in $PATH: \"typescript-language-server\"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at start (/$bunfs/root/src/entrypoints/cli.js:3133:20831)\n at A (/$bunfs/root/src/entrypoints/cli.js:3133:24600)\n at O (/$bunfs/root/src/entrypoints/cli.js:3133:33741)\n at j (/$bunfs/root/src/entrypoints/cli.js:3133:34078)\n at z (/$bunfs/root/src/entrypoints/cli.js:3133:34628)\n at call (/$bunfs/root/src/entrypoints/cli.js:3161:1270)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:03:59.141Z"},{"error":"Error: Cannot send notification to LSP server 'plugin:typescript-lsp:typescript': server is error\n at f (/$bunfs/root/src/entrypoints/cli.js:3133:27015)\n at j (/$bunfs/root/src/entrypoints/cli.js:3133:34332)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:04:00.828Z"},{"error":"Error: Failed to sync file open /Users/m/Dev/AI/edge-protocol/test/commands/list-episodes.test.ts: Cannot send notification to LSP server 'plugin:typescript-lsp:typescript': server is error\n at j (/$bunfs/root/src/entrypoints/cli.js:3133:34497)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:04:00.828Z"},{"error":"Error: Failed to sync file open /Users/m/Dev/AI/edge-protocol/test/commands/list-episodes.test.ts: Cannot send notification to LSP server 'plugin:typescript-lsp:typescript': server is error\n at j (/$bunfs/root/src/entrypoints/cli.js:3133:34497)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:04:00.829Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/m/Dev/AI/edge-protocol.\n at call (/$bunfs/root/src/entrypoints/cli.js:4321:6398)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:13:56.929Z"},{"error":"Error: Cannot send notification to LSP server 'plugin:typescript-lsp:typescript': server is error\n at f (/$bunfs/root/src/entrypoints/cli.js:3133:27015)\n at j (/$bunfs/root/src/entrypoints/cli.js:3133:34332)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-02T04:16:17.844Z"},{"error":"Error: Failed to sync file open /Users/m/Dev/AI/edge-protocol/src/config/env.ts: Cannot send notification to LSP server 'plugin:typescr…Note: Content was truncated.
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
The 0% session usage + rate limit triggered pattern points to server-side accounting rather than the client-side cache bug. Two things worth checking:
organizationUuid, not individual account. If anyone else shares your billing method or org, their usage counts against your pool. This was confirmed via source code analysis of thepassesEligibilityCacheandoverageCreditGrantCachefunctions (#41881)./usage. Updating to v2.1.90 won't fix the server-side accounting mismatch, but it will at least ensure your actual token usage is efficient.The 2-hour discrepancy between the error reset time and
/usagereset time is a separate bug that several others have reported as well.More on the org-level quota structure and cache measurement methodology: https://github.com/ArkNill/claude-code-cache-analysis
@ArkNill
Thanks for the comment.
It was resolved in about 10 minutes. It seems the recent plan change took some time to take effect.
April 3 update: v2.1.91 fixes the cache regression that caused the worst drain. If you are still hitting limits after updating, there are additional unfixed mechanisms: a 200K tool result budget cap, a client-side false rate limiter, and silent context stripping — all confirmed via proxy testing. Anthropic acknowledged peak-hour tightening on X (Lydia Hallie) but stated "none were over-charging you." Measured data and analysis: claude-code-cache-analysis
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.