claude-code - 💡(How to fix) Fix [Bug] Unexpected increase in token consumption rate [2 comments, 2 participants]

[{"error":"Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011Ca5jQjRin6XQZ9wA4u3Gh"}\n at i4.generate (file:///C:/Users/Info/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:8:50830)\n at qI.makeStatusError (file:///C:/Users/Info/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:47:2195)\n at qI.makeRequest (file:///C:/Users/Info/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:47:5420)\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)","timestamp":"2026-04-15T14:41:44.036Z"},{"error":"Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011Ca5jRAMfa44GwT7e5ySzR"}\n at i4.generate (file:///C:/Users/Info/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:8:50830)\n at qI.makeStatusError (file:///C:/Users/Info/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:47:2195)\n at qI.makeRequest (file:///C:/Users/Info/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:47:5420)\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)","timestamp":"2026-04-15T14:41:49.505Z"}]

TL;DR

The issue may be related to changes in token usage or an internal server error, and contacting support or checking the release notes for any updates on token usage changes could help resolve the issue.

Guidance

• Review the release notes for any updates on token usage changes that may have been implemented in version 2.1.87.
• Check the error messages for any patterns or clues that could indicate the cause of the internal server error.
• Consider reaching out to support with the provided Feedback ID (1822be30-2690-48df-a6ee-e8db2750e37a) for further assistance.
• Monitor token usage to see if there are any specific actions or features that are causing the increased usage.

Example

No code snippet is provided as the issue does not seem to be related to a specific code problem.

Notes

The issue lacks specific technical details about the changes in token usage or the internal server error, making it difficult to provide a more detailed solution.

Recommendation

Apply workaround: Contact support for further assistance, as they may be able to provide more information on the token usage changes or internal server error.