claude-code - 💡(How to fix) Fix [Bug] Session limit exceeded causes unexpectedly high token consumption rate [2 comments, 3 participants]

[{"error":"Error: Request was aborted.\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T16:07:31.361Z"},{"error":"MaxFileReadTokenExceededError: File content (44817 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 pp7 (B:/~BUN/root/src/entrypoints/cli.js:4914:12772)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T16:07:45.132Z"},{"error":"MaxFileReadTokenExceededError: File content (56093 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 pp7 (B:/~BUN/root/src/entrypoints/cli.js:4914:12772)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T16:07:54.936Z"},{"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_011CaeEc4MK4CBUmaX26nkSQ"}\n at generate (B:/~BUN/root/src/entrypoints/cli.js:11:57304)\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-02T18:43:31.069Z"}]

TL;DR

The issue is likely due to exceeding the rate limit or maximum allowed tokens, causing funds to decrease rapidly.

Guidance

• The MaxFileReadTokenExceededError suggests that the file content exceeds the maximum allowed tokens (25000), which may be contributing to the issue.
• The rate_limit_error in the last error message indicates that the account's rate limit has been exceeded, which could also be a factor.
• To mitigate this, consider using the offset and limit parameters to read specific portions of the file, as suggested in the error message.
• Reviewing the request frequency and adjusting it to avoid exceeding the rate limit may also help.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to the version (2.1.126) or the platform (win32), but without further information, it is difficult to determine the exact cause.

Recommendation

Apply workaround: Adjust the request frequency and use offset and limit parameters to avoid exceeding the rate limit and maximum allowed tokens, as this is a more immediate and feasible solution given the provided information.