[BUG] Possible Usage Credits Re-enabling and Runaway Usage/Billing After Claude Code Update and Commit Action

[fruzelee]

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?

On July 15, 2026, I experienced a severe unexpected usage and billing incident while using the official Claude Code GUI.

Before the incident, Usage Credits were disabled in my account.

The observed sequence was:

1. I installed a Claude Code update.
2. I was using the Opus model and performed a single Git commit action through the Claude Code GUI as part of my normal development workflow.
3. Shortly afterward, Claude Code usage began increasing extremely rapidly.
4. My usage limits were exhausted within minutes.
5. Fable usage appeared even though I had not intentionally selected or used the Fable model.
6. Usage Credits appeared to become active despite previously being disabled.
7. I attempted multiple times to disable Usage Credits, but the setting appeared to become enabled again before I was eventually able to turn it off.
8. I manually reduced the spending limit during the incident in an attempt to contain the unexpected charges, first to $100, then $20, and eventually $1.
9. Multiple unexpected billing events were generated, totaling $382.54.

The Usage Credits dashboard later showed approximately $263.61 in usage credits spent, and the account balance showed -$0.01.

I did not intentionally initiate a long-running agent task, select the Fable model, enable Usage Credits, or authorize the resulting abnormal usage.

The issue appears to involve a possible combination of:

• unexpected runaway usage after a commit action;
• Usage Credits state not consistently persisting after being disabled;
• unexpected model attribution;
• unexpected plan/billing state changes.

I cannot determine the exact technical cause and am not claiming a definitive root cause. However, the sequence appears reproducible as a potential software or account-state anomaly and should be investigated.

The incident caused a significant financial impact. The total unexpected charges were $382.54, of which $247.08 remains disputed after a separate prorated subscription refund.

Relevant context:

• Product: Claude Code official GUI
• Date: July 15, 2026
• Model intentionally used: Opus
• Model unexpectedly appearing in usage: Fable
• Usage Credits: disabled before incident; repeatedly attempted to disable during incident
• Unexpected usage: approximately $263.61
• Total charges: $382.54
• Remaining disputed amount: $247.08

I can provide screenshots and additional private evidence to the appropriate team if required.

The version i was using was most probable is Claude Code 2.1.208, i guess while facing the issue billing.

What Should Happen?

When a user performs a normal Git commit action from the Claude Code GUI, Claude Code should only perform the requested commit operation and should not unexpectedly start or continue an unbounded agent process, rapidly consume usage limits, switch models, enable Usage Credits, change subscription or billing settings, or generate unexpected API charges.

Usage Credits should remain disabled unless the user explicitly enables them, and a disabled setting should not become enabled again without a clear, intentional user action.

If a commit-related process encounters an error, loop, or unexpectedly high usage, Claude Code should stop or enforce appropriate runaway-loop and usage safeguards rather than continuing to consume usage and generate substantial charges without clear user confirmation.

In my case, the behavior I observed was the opposite: after updating Claude Code and performing a single commit action, usage increased extremely rapidly, usage limits were exhausted within minutes, Fable usage appeared even though I had intentionally been using Opus, and Usage Credits appeared to become active despite having previously been disabled.

Error Messages/Logs

Steps to Reproduce

The Claude Code version involved was most likely 2.1.208, although I cannot confirm the exact version with absolute certainty. The incident occurred around the time I updated Claude Code and then performed a commit action through the GUI. I later became aware that subsequent Claude Code releases, including 2.1.211 and 2.1.212, included changes related to billing behavior and runaway-loop limits. I am providing this version information as approximate context and not claiming that a specific release was definitively the root cause.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.210

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

Relevant context:

• Product: Claude Code official GUI
• Date: July 15, 2026
• Model intentionally used: Opus
• Model unexpectedly appearing in usage: Fable
• Usage Credits: disabled before incident; repeatedly attempted to disable during incident
• Unexpected usage: approximately $263.61
• Total charges: $382.54
• Remaining disputed amount: $247.08