claude-code - 💡(How to fix) Fix [BUG] "Hello" = 19% usage on a Max Plan [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#45042Fetched 2026-04-09 08:14:38
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2commented ×1unlabeled ×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 single 'hello' in the Code module of the Claude Code MacOS app directly consumed 19% of my current session's usage.

<img width="960" height="429" alt="Image" src="https://github.com/user-attachments/assets/9b55feb6-f5fb-4ba5-8fb9-ca10b831a74a" />

The app version is Claude 1.1062.0 (b81bcd) 2026-04-06T21:20:28.000Z.

Also, customer support is completely unreachable.

What Should Happen?

2 weeks ago, the usage increment was normal.

Error Messages/Logs

Steps to Reproduce

Just send a 'hello' to any previous session in the Code view of Claude Code app on MacOS

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.1062.0 (b81bcd) 2026-04-06T21:20:28.000Z

Platform

Other

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

No response

extent analysis

TL;DR

The issue can likely be mitigated by reverting to a previous version of Claude Code that worked as expected, given that it's identified as a regression.

Guidance

  • Verify the last working version of Claude Code to understand when the regression occurred.
  • Attempt to reproduce the issue in a controlled environment to confirm the steps to reproduce are accurate and reliable.
  • Consider reaching out to the development team or community forums for assistance, as customer support is currently unreachable.
  • If possible, test the same functionality in a different platform or version to isolate if the issue is specific to MacOS or the Opus model.

Example

No specific code example can be provided without more context on the Claude Code API or functionality.

Notes

The lack of response in the "Last Working Version" and "Additional Information" sections limits the ability to provide a more targeted fix. The unreachability of customer support also complicates the process of reporting and resolving the issue directly with the developers.

Recommendation

Apply workaround: Given the regression nature of the issue and the unavailability of customer support, reverting to a previous version or finding an alternative workaround seems to be the most viable immediate solution.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING