claude-code - 💡(How to fix) Fix [BUG] Current Session % jumped up from astronomically during non high burn times. [1 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#54201Fetched 2026-04-29 06:33:35
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×2unlabeled ×1

Error Message

Error in current session burn times. This happens on off-peak...

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?

Error in current session burn times. This happens on off-peak...

What Should Happen?

Credit for all users

Error Messages/Logs

Steps to Reproduce

NA

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

NA

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue may be resolved by investigating the changes made between the last working version and the current version of Claude Code to identify the cause of the error in current session burn times.

Guidance

  • Review the commit history to find the last working version and compare it with the current version to identify potential changes that could be causing the issue.
  • Check the Anthropics API documentation to see if there have been any updates or changes that could be affecting the session burn times.
  • Since this is a regression, try to reproduce the issue in a controlled environment to gather more information about the error.
  • Consider reaching out to the development team or checking the GitHub issues page for any similar reports or fixes related to session burn times.

Notes

The lack of information about the last working version and the error messages/logs makes it difficult to provide a more specific solution. Additionally, without more details about the changes made between versions, it's hard to pinpoint the exact cause of the issue.

Recommendation

Apply workaround: Try to identify the changes made between the last working version and the current version and revert or modify them to see if it resolves the issue, as the problem is reported as a regression and the last working version is not specified.

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

claude-code - 💡(How to fix) Fix [BUG] Current Session % jumped up from astronomically during non high burn times. [1 participants]