Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix 🐛 [Bug] Follow-up to #29108 — Systemic billing failure corroborated by multiple issues — Credit restoration requested [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#53292•Fetched 2026-04-26 05:19:28
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
jrbsolucoesjrbsolucoes
Participants
jrbsolucoesjrbsolucoes
Timeline (top)
labeled ×4

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?

This is a follow-up to #29108, which was auto-closed and locked by the bot before receiving any response from the Anthropic engineering team.

Anthropic's own support team (conversation #215473516500734) confirmed a billing system failure during my session on 2026-02-25 and issued a partial refund of $2.70 — establishing that the system was not behaving normally during my first ever Claude Code session.

Since #29108 was filed, four issues were automatically linked to it, all describing the same root behavior:

  • #36669 — Background tasks cause rapid usage over hours despite idle compute
  • #41430 — Idle time is included in session time
  • #42734 — Stuck/zombie sessions consume API quota while unresponsive
  • #41666 — Yanked release caused wasted session and significant token loss

Total consumed: $39.07 out of $45.00 loaded. Partial refund of $2.70 issued. Remaining $36.37 in dispute.

What Should Happen?

Credits should not be consumed by background/zombie processes after session close. Deleting an API key should immediately halt all charges. Users should have access to per-session spending caps.

I am requesting $36.37 in API credit restoration — not a cash refund — so I can continue building with Claude Code.

Error Messages/Logs

Steps to Reproduce

  1. Load prepaid API credits with auto-reload DISABLED
  2. Open Claude Code and start an interactive session (scaffolding/planning)
  3. Close the Claude Code session normally
  4. Check billing dashboard the next morning
  5. Observed: credits continued draining after session close and after API key deletion

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.59

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

Account: [email protected] Support conversation: #215473516500734 Original issue: #29108 Amount still in dispute: $36.37

Anthropic support acknowledged billing system failure and issued partial refund of $2.70. The remaining $36.37 was attributed to "valid API activity" without providing an itemized log. Itemized log was formally requested and not provided.

extent analysis

TL;DR

The most likely fix is to wait for the Anthropic engineering team to address the billing system failure and implement a solution to prevent credits from being consumed by background/zombie processes after session close.

Guidance

  • Verify that the issue is indeed related to the billing system failure acknowledged by Anthropic support, and that the partial refund of $2.70 was issued correctly.
  • Check the billing dashboard to see if there are any ongoing charges that can be halted by deleting the API key or taking other measures.
  • Consider reaching out to Anthropic support again to request an itemized log of the "valid API activity" that contributed to the remaining $36.37 in dispute.
  • Review the terms of service and usage guidelines to understand how credits are consumed and what constitutes "valid API activity".

Notes

The issue seems to be related to a billing system failure, and the Anthropic support team has already acknowledged the issue and issued a partial refund. However, the remaining amount in dispute is still unclear, and an itemized log has not been provided.

Recommendation

Apply workaround: Wait for the Anthropic engineering team to address the billing system failure and implement a solution to prevent credits from being consumed by background/zombie processes after session close, as the issue is likely related to a regression in the billing system.

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#inference speed#output truncation#response parsing#generation 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