claude-code - 💡(How to fix) Fix You're out of extra usage · resets 2pm (America/Chicago) [2 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/petersykim/.local/share/claude/versions/2.1.117 (expected in multi-process scenarios)\n at fn_ (/$bunfs/root/src/entrypoints/cli.js:2754:2177)\n at H98 (/$bunfs/root/src/entrypoints/cli.js:2754:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T17:15:23.434Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/Users/petersykim/Desktop/New Folder With Items'\n at J1H (/$bunfs/root/src/entrypoints/cli.js:1696:144)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T17:16:18.110Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T19:33:54.612Z"},{"error":"Error: Failed to fetch version from https://downloads.claude.ai/claude-code-releases/latest: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at xi1 (/$bunfs/root/src/entrypoints/cli.js:2752:5520)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T21:45:42.387Z"},{"error":"Error: Failed to fetch version from https://downloads.claude.ai/claude-code-releases/latest: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at xi1 (/$bunfs/root/src/entrypoints/cli.js:2752:5520)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T21:45:42.388Z"},{"error":"MaxFileReadTokenExceededError: File content (44566 tokens) exceeds maximum allowed tokens (25000). 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 KW7 (/$bunfs/root/src/entrypoints/cli.js:4737:12658)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T22:08:39.969Z"},{"error":"MaxFileReadTokenExceededError: File content (37889 tokens) exceeds maximum allowed tokens (25000). 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 KW7 (/$bunfs/root/src/entrypoints/cli.js:4737:12658)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T22:09:40.751Z"},{"error":"Error: 429 {"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your account's rate limit. Please try again later."},"request_id":"req_011CaKavTYLWyFdPPRBZrVXL"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:54524)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T22:18:39.379Z"},{"error":"Error: 429 {"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your account's rate limit. Please try again later."},"request_id":"req_011CaKdz6LM2wU5Ay1oCq9DJ"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:54524)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T22:58:49.047Z"}]

TL;DR

The account upgrade from 5x to 20x plan may have triggered a bug that miscalculated the usage amount, causing the account to be locked out due to exceeding the rate limit.

Guidance

• The error messages indicate that the account is experiencing rate limit errors (429) and MaxFileReadTokenExceededError, suggesting that the usage calculation issue is related to the account's rate limits.
• The AI agent's suggestion that there may be a bug in the usage calculation when the account is upgraded should be investigated further.
• To mitigate the issue, it may be possible to contact the support team to manually adjust the usage calculation or provide a temporary rate limit increase.
• Reviewing the account's usage patterns and adjusting them to be within the rate limits may also help prevent similar issues in the future.

Example

No code snippet is provided as the issue seems to be related to the account's configuration and usage patterns rather than a specific code error.

Notes

The provided error messages and environment information do not provide a clear technical root cause, and the issue may require further investigation and support from the development team.

Recommendation

Apply workaround: Contact the support team to manually adjust the usage calculation or provide a temporary rate limit increase, as the issue seems to be related to a bug in the usage calculation when the account is upgraded.