Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Abnormal compute consumption: 5-hour Max Plan quota exhausted in 7 minutes during minor refactor [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55030•Fetched 2026-05-01 05:48:05
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Developer-O1Developer-O1
Participants
Developer-O1Developer-O1github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

A minor refactoring task performed via Claude Code resulted in a 100% depletion of the "5-hour compute limit" within approximately 7 minutes of real-time usage. This suggests a critical failure in the usage calculation logic or an inefficient file-scanning loop (OOM/Token-burn) when processing project structures.

Context Plan: Max

Tool: Claude Code (CLI)

Time spent: ~7 minutes

Task: Adding 6 CSS status tokens to types.ts, applyTheme.ts, and 3 theme files, plus replacing hardcoded Tailwind classes in ~15 React components.

Actual Behavior The system flags the 5-hour limit as completely exhausted, effectively locking the user out of the service.

What Should Happen?

Proportional Consumption: A 7-minute session involving minor text edits and token updates should consume approximately 2-5% of the 5-hour quota, leaving the vast majority of the "compute time" for actual complex development work.

Efficient Scanning: The tool should respect project boundaries (like .gitignore) and only process relevant source files, rather than burning through the entire context window for simple string replacements.

Predictable Limits: As a Max Plan subscriber, I expect the "5-hour limit" to reflect 5 hours of active, high-intensity reasoning, not a few minutes of file indexing.

Accurate Tracking: If a task is about to consume a massive amount of credit (due to a large file scan), the tool should provide a warning or a progress indicator before exhausting the entire daily/weekly quota in one go.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce Initialize Claude Code in a React/Tailwind project.

Request a project-wide scan to identify hardcoded color strings

Apply changes to approximately 10–20 files.

Observe the usage quota jumping from <5% to 100% immediately after the operation.

Expected Behavior A 7-minute session involving minor text replacements should consume a negligible fraction of the 5-hour professional quota.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.123

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by optimizing the file-scanning loop in Claude Code to respect project boundaries and only process relevant source files.

Guidance

  • Review the project structure and ensure that the .gitignore file is correctly configured to exclude unnecessary files from the scan.
  • Consider implementing a more efficient scanning algorithm that can handle large projects without exhausting the compute limit.
  • Verify that the usage calculation logic is accurate and not overestimating the compute time required for minor text edits and token updates.
  • Test the tool with a smaller project to see if the issue persists, which can help determine if the problem is related to project size or complexity.

Example

No code snippet is provided as the issue does not contain sufficient information about the specific code changes made.

Notes

The issue may be related to a regression in the Claude Code version 2.1.123, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Optimize the file-scanning loop to improve efficiency and reduce compute time consumption, as the issue is likely related to the tool's handling of large projects.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Abnormal compute consumption: 5-hour Max Plan quota exhausted in 7 minutes during minor refactor [1 comments, 2 participants]