Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] close to ridiculously usage limits. 4 messages and 50 percent used in peak at 5x max. [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#55090•Fetched 2026-05-01 05:46:30
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
3
Author
sorcrr-devsorcrr-dev
Participants
github-actions[bot]github-actions[bot]sorcrr-devsorcrr-dev
Timeline (top)
labeled ×4commented ×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?

usage limits are a bit too brutal. if this continues, will be switching over to codex. this peak hour usage limit where 8 messages and the entire thing is up is just ridiculous. you guys just picked up 40 billion dollars. whats with the stinginess.

What Should Happen?

should be back to the way it was - no peak usage limits and atleast 50 messages - match codex. otherwise it makes no sense.

Error Messages/Logs

Steps to Reproduce

open up two instances, send a message, and watch 30 percent just vanish as you resume typically around 70 - 80 percent context remaining on resume. then send a message and goes to 45 by the end of the first round. Each round takes up 8 - 15 percent. just ridiculous. not a good feeling to be so concerned about running out.

Claude Model

None

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

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by adjusting usage patterns to avoid peak hour limits or exploring alternative models with more generous limits.

Guidance

  • Review the Anthropic API documentation to understand the current usage limits and pricing model.
  • Consider optimizing message sending to avoid peak hours or batches to minimize the impact of usage limits.
  • Evaluate alternative models, such as Codex, to determine if they offer more suitable usage limits for the specific use case.
  • If the issue is indeed a regression, try to identify the last working version and compare its usage limits to the current version.

Notes

The provided information lacks specific details about the previous version's usage limits and the exact changes that led to the current issue. Therefore, it's challenging to provide a definitive solution.

Recommendation

Apply workaround: Adjust usage patterns to avoid peak hour limits, as the current version's limits seem to be the primary cause of the issue.

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#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING