Skip to content

[BUG] Since mid-November, claude code is consuming ~5x tokens #13552

Closed as not planned

Description

@kglowacki

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?

I use Claude Code PRO across various projects and noticed very high usage comparing to previous months. Either it is using way more tokens, or Anthropic has changed token counting rules w/o telling anyone. In both cases users are paying the price.

What Should Happen?

Token usage and work time should stay relatively the same under similar circumstances.

Error Messages/Logs

Steps to Reproduce

  1. Start working with Claude Code on any task
  2. You'll hit usage limit 5x faster than in October.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.0.64

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

Activity

  1. github-actions commented on Dec 10, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] Version 2.0.61 is extremely slow and causes rapid, excessive token consumption/rate limits #13466
    2. [Bug] Excessive token usage on new session initialization #13536
    3. [Bug] Max plan usage consumed at unusually high rate without workflow changes #13551

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. yambu commented on Dec 10, 2025

    @yambu

    Same here

  3. kglowacki commented on Dec 10, 2025

    @kglowacki
    Author

    btw, just starting Claude, w/o giving it any commands, can consume up to 4% of allowed session limit xD... sorry boys, this is simply against terms of service. Starting a tool is not counted as 'usage'.

  4. rbarcante commented on Dec 10, 2025

    @rbarcante

    Same thing here @kglowacki

  5. MacieGx commented on Dec 10, 2025

    @MacieGx

    Same here, I've been seeing the same spike in token usage since mid-November. I'm on Claude Code 2.0.55, so it doesn't seem limited to the newest versions.

  6. grandtheftdisco commented on Dec 12, 2025

    @grandtheftdisco

    Same here. Hitting a 5 hour limit within 30 minutes without any change in my workflow.

  7. grandtheftdisco commented on Dec 12, 2025

    @grandtheftdisco

    ⭐ TIPS:
    I've been browsing similar area:cost issues re: Claude this morning and have gathered a few tips in one place. These don't fix the issue entirely but they've helped cut down my usage in the interim: hope these help someone!

    1. direct Claude to not use Task feature, and to use utility tools for common tasks. Add –no-agent flag to your prompt as well (several users reporting that Claude is recruiting subagents without disclosing this to the user)
    • ie “ --no-agent for the remainder of our work in this session. DO NOT use the Task tool. Use Grep to find files, Read to check them, and Edit to fix them directly."
    1. use /config in the CLI to disable auto-compact, as this is another source of token overconsumption

    If anyone else finds ways to reduce token consumption while we wait, feel free to share! 👍

  8. github-actions commented on Jan 14, 2026

    @github-actions

    This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

  9. github-actions commented on Feb 14, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  10. github-actions commented on Feb 21, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  11. locked as resolved and limited conversation to collaborators on Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:costautocloseIssue will be closed automaticallybugSomething isn't workinghas reproHas detailed reproduction stepsplatform:macosIssue specifically occurs on macOS

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions