Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Usage spikes drastically after /compact command and even after running claude [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#53018•Fetched 2026-04-25 06:14:35
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Jagadish-RapuruJagadish-Rapuru
Participants
github-actions[bot]github-actions[bot]Jagadish-RapuruJagadish-Rapuru
Timeline (top)
labeled ×3closed ×1commented ×1renamed ×1

Error Message

Error Messages/Logs

No error messages shown. Usage bar visually jumped to 100%

Code Example

No error messages shown. Usage bar visually jumped to 100% 
with a warning icon after running claude --version
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?

Environment

  • Claude Code version: 2.1.119
  • Plan: Claude Max 5x ($100/month)
  • Model: Opus 4.7 (1M context)
  • Reset time: 6:00 PM

Issue Summary

After running the /compact command with a small prompt, usage jumped approximately 34% in a single operation. Before /compact the usage was at a lower level and after it completed, usage showed 64%.

Shortly after, running "claude --version" which is a local command that requires NO API call and NO server communication, caused usage to jump from 64% to 100%.

What Should Happen?

  • /compact with a small prompt should have minimal usage impact
  • "claude --version" is a local command and should consume ZERO tokens and ZERO usage under any circumstances
  • Users should receive a warning before /compact runs that it may consume significant usage

Error Messages/Logs

No error messages shown. Usage bar visually jumped to 100% 
with a warning icon after running claude --version

Steps to Reproduce

  1. Start a Claude Code session with some conversation history
  2. Run /compact command with a small minimal prompt
  3. Observe usage bar jumping approximately 34% immediately
  4. Run "claude --version" in terminal
  5. Observe usage jumping from 64% to 100% despite no API call being made

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

This is directly affecting paid subscribers on the Claude Max plan ($100/month). Usage limits are being consumed by operations that either should not count at all or are disproportionately high without any warning. This results in lost paid usage with no recourse for refund as per Anthropic support response.

This appears to be part of a wider pattern reported by multiple Max plan subscribers where usage limits are being hit unexpectedly faster than before.

extent analysis

TL;DR

The issue can be mitigated by avoiding the use of the /compact command with small prompts and refraining from running claude --version after compacting, as these actions are causing unexpected usage spikes.

Guidance

  • Investigate the implementation of the /compact command to understand why it's causing a 34% usage jump with small prompts, and consider optimizing it for minimal usage impact.
  • Verify that the claude --version command is indeed not making any API calls or server communications, as it should not consume any tokens or usage.
  • Test the usage impact of running claude --version in isolation, without preceding /compact commands, to determine if it's a cumulative effect or an independent issue.
  • Consider adding a warning to the /compact command to inform users of potential significant usage consumption.

Example

No code snippet is provided as the issue is more related to the usage and behavior of the Claude Code application rather than a specific code error.

Notes

The issue seems to be part of a wider pattern affecting Max plan subscribers, suggesting a potential regression or misconfiguration in the latest version of Claude Code. The lack of information on the last working version makes it difficult to pinpoint the exact cause.

Recommendation

Apply workaround: Avoid using the /compact command with small prompts and refrain from running claude --version after compacting, as these actions are causing unexpected usage spikes. This is recommended because it can help mitigate the issue until a permanent fix is found, especially considering the financial impact on paid subscribers.

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#conversation history#authentication issue#prompt issue#agent setup

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 Usage spikes drastically after /compact command and even after running claude [1 comments, 2 participants]