claude-code - 💡(How to fix) Fix [BUG] Using the same prompt and model at different times results in higher token consumption during later executions. [2 comments, 3 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#47967Fetched 2026-04-15 06:37:13
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Timeline (top)
labeled ×5commented ×2

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?

Version information:

Identifier: anthropic.claude-code Version: 2.1.107 Last Updated: 2 hours ago Size: 241.01 MB

What Should Happen?

Version information:

Identifier: anthropic.claude-code Version: 2.1.107 Last Updated: 2 hours ago Size: 241.01 MB

Error Messages/Logs

Steps to Reproduce

Version information:

Identifier: anthropic.claude-code Version: 2.1.107 Last Updated: 2 hours ago Size: 241.01 MB

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.107

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue is likely related to a regression in version 2.1.107 of Claude Code, and the user should try to identify the last working version to help pinpoint the cause.

Guidance

  • Since the issue is reported as a regression, comparing changes between the current version (2.1.107) and the last known working version could help identify the root cause.
  • The user should attempt to recall or find the last working version of Claude Code to provide more specific information for debugging.
  • Given the lack of specific error messages or logs, reproducing the issue with detailed logging enabled might provide crucial insights into what's going wrong.
  • Checking the release notes or changelog for version 2.1.107 and subsequent versions might highlight changes that could be related to the regression.

Notes

The provided information lacks specific details about the error or the changes made in the recent version, making it challenging to provide a precise fix. More details about the last working version and any error messages would be necessary for a more targeted approach.

Recommendation

Apply workaround: The user should focus on identifying the last working version and comparing it with the current version to find a potential workaround or fix for the regression.

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