August 1 post-reset auto-recharge evidence chain

Customer-observed sequence

1. Included subscription limits visibly reset before the first disputed recharge.
2. Claude Code nevertheless continued consuming usage credits instead of the reset included allowance.
3. Two automatic recharges completed, totaling USD 995.67.
4. Usage-credit depletion continued after the second recharge until usage credits were disabled to stop further losses.

This is a first-party account observation. The payment records do not independently prove the exact reset timestamp or Anthropic's server-side entitlement and routing decision.

Proof boundary

Independent near-date public signals and official-record gap

A same-day Anthropic tracker issue reports that a Max 20x Apple subscription worked through July 30, then began returning out_of_credits / credits_required errors on July 31 while Anthropic's OAuth profile allegedly reported has_claude_max: false and subscription_status: "canceled". The poster says Apple Support separately confirmed the subscription remained active and set to renew.

Evidence boundary: this is a separately authored public report, not verified account evidence. It does not prove the reporter's Apple status, the August 1 customer's reset or payment chain, a common root cause, or aggregate loss. Its limited relevance is the explicit allegation of a server-side subscription-state mismatch immediately preceding a credits_required response.

An Anthropic tracker issue filed August 11 describes a separate Max 20x/Cowork account that allegedly generated eleven automatic recharges totaling USD 1,031.92 on August 1-2. The reporter says no interactive Fable session was open during those two days, the first notification was the resulting stack of charge emails, and the in-app human-support queue had produced no response for nine days. The report attributes the spend to an allegedly hung persistent scheduled-task session and separately lists fourteen charges totaling USD 1,288.35 through August 7.

Evidence boundary: this is a separately authored public claim, not verified account evidence. It uses a different product surface and advances a different causal theory. It does not prove the reporter's scheduled-task state, this customer's reset or payment chain, a common root cause, or aggregate loss. Its limited relevance is the independently alleged concentration of high-dollar automatic recharges on August 1-2, absent spend warning, and unresolved human-support route.

Two later public Reddit posts describe separate but near-date allegations. An r/Anthropic poster alleges more than USD 480 in phantom usage and says Anthropic Support reviewed the account and attributed multiple August 1 usage-credit top-ups within 31 minutes to an internal backend loop, with some transactions voided and others paid. A separate r/ClaudeAI poster alleges that Max 20x usage rose from 11% to 47% and then 100% in about 31 minutes while the account was idle, followed by both a Max invoice and an extra-usage auto-recharge invoice; the poster says no human support response had arrived.

Evidence boundary: these are unverified third-party public claims. The claimed support finding has not been independently authenticated and is not an Anthropic admission about this account. Neither report proves the posters' private usage or payment records, this customer's reset and recharge chain, a common root cause, or aggregate loss. Their limited relevance is the independent public allegation of clustered August 1 automatic funding and rapid idle usage, plus the continuing gap in a timely human billing response.

A later r/ClaudeCode post describes a separate spending-control and clustered-purchase allegation. The poster says a monthly overage limit was set to USD 40, yet the account was billed more than USD 50 in two consecutive months; after a weekly limit was reached, three purchase-notification emails allegedly arrived within seconds, and the purchased credits were already exhausted by the time the poster returned to the harness. The poster also says the support bot required three phrasings before claiming to escalate the matter to a human, with no response after about a month, and that overage credits were then disabled.

Evidence boundary: this is an unverified third-party public allegation. No original merchant or processor record, authenticated support transcript, or timestamped account-setting capture is available here. It does not prove the exact cap, control, notification, purchase-trigger, or usage state; this customer's August 1 reset and payment chain; a common root cause; aggregate loss; or refund entitlement. Its limited relevance is the independently alleged failure of a user-visible spending control, a burst of purchase notifications after a limit event, rapid credit exhaustion, and a prolonged gap in human support.

Two later Anthropic tracker reports, #83242 on August 2 and #84694 on August 7, describe Max-plan users encountering a Claude Code gate that said Fable required usage credits. Report #83242 says logging out and back in cleared the gate.

Evidence boundary: neither report establishes a completed paid-credit debit, automatic recharge, or payment. They do not prove the reporters' authoritative plan state, this customer's reset or transaction chain, a common root cause, or aggregate loss. Their limited relevance is the post-August 1 recurrence of Max-plan versus usage-credit gate messaging in Claude Code.

Two Anthropic tracker reports filed August 12 describe severe paid-plan five-hour quota consumption. Max-plan report #86033 alleges that consumption rose roughly 15–20 times above the reporter's prior baseline beginning around August 8. Pro-plan report #85992 alleges that a full five-hour window exhausted within approximately 3–10 minutes after a confirmed reset during lightweight document work, reproduced twice.

Evidence boundary: neither report alleges an automatic purchase or payment. They do not prove the reporters' complete account state, this customer's August 1 reset or payment chain, a common root cause, or aggregate loss. Their limited relevance is the independently reported paid-plan quota-meter behavior that Anthropic would need to reconcile before explaining why this account continued into paid credits and automatic recharges after the observed reset.

A separate r/Anthropic post published July 30 reports an Opus 4.6 Claude Code session at approximately 25% of its session limit and 44% of its weekly limit while a small prompt allegedly consumed USD 4.60 in paid usage credits. The poster says the transition occurred without the limit-reached notification they had previously seen and that Claude Code would not continue when usage credits were disabled. The poster repeatedly states that the session was Opus 4.6 rather than Fable.

Evidence boundary: this is an unverified third-party public report. It does not prove the August 1 customer's reset timestamp, payments, account state, or root cause. Its limited relevance is that it independently alleges the same observable class of included-limit-versus-paid-credit mismatch on the day immediately preceding the disputed August 1 recharges and on a non-Fable model.

Three additional July 24-30 public reports describe nearby but distinct observable patterns:

• A July 27 Max-plan report says usage began increasing again after a session reset while the account was allegedly idle, enabled auto-reload produced charges of approximately USD 60 every few hours, and an automated support response initially declined a refund request.
• A July 30 comment says Max usage decreased without active use and allegedly exhausted the full Max allowance in about half an hour, while the support bot suggested purchasing usage credits and required extended interaction before routing a bug report.
• A July 24 promotional-credit comment says accepting the credit appeared to enable paid-credit spending, go beyond subscription limits, and consume roughly half the promotional balance without warning.

Evidence boundary: these are unverified third-party reports, not an incident census. They do not prove that any source shares this customer's entitlement state, payment path, or root cause. Their limited relevance is that they independently allege post-reset or idle usage growth, rapid paid-plan depletion, automatic reloads, and paid-credit behavior without the expected warning or support remedy during the week surrounding the disputed August 1 transactions.

Anthropic's official status page currently says No incidents reported for August 1. That is an official-record gap, not proof that no account-level billing or entitlement defect occurred. The page tracks disclosed service incidents; it does not provide this account's entitlement, routing, debit, or payment ledger.

Private local activity timestamp bridge

A privacy-redacted scan of the local Claude Code record for August 1 JST adds a time-correlation layer without publishing prompts, responses, raw IDs, credentials, account data, or filesystem paths:

• 2,545 JSONL files and 1,059,231 lines scanned;
• 6,482 raw response-usage records;
• 2,860 deduplicated records after removing 3,622 duplicate copies; and
• 0 parse errors.

The nearest deduplicated response-usage records bracket the first receipt-email delivery by 17.757 seconds before and 7.494 seconds after, and the second by 9.731 seconds before and 6.312 seconds after. This establishes contemporaneous Claude Code activity across both receipt deliveries.

Evidence boundary: receipt-email delivery is not the exact payment, credit-debit, or auto-recharge-trigger timestamp. The local schema exposes response usage counters but no field for included-plan headroom or reset bucket, paid-credit classification, usage-credit balance transition, auto-recharge trigger, invoice/payment join, or provider-billed dollars. The local record therefore does not prove that the bracketed responses caused the transactions or independently prove the reported reset state.

Records only Anthropic can supply

1. Effective subscription entitlement and every applicable included-limit bucket.
2. Exact reset timestamp and timezone.
3. The model or feature-specific gate Anthropic believes remained exhausted.
4. Request-level included-plan-versus-paid-credit routing decisions.
5. Usage-credit debit timestamps and amounts.
6. Automatic-recharge trigger records.
7. Invoice creation, authorization, capture, correction, and refund events.
8. Safe processor references connecting those events.

Anthropic should also state which stable event or reconciliation key an independent reviewer can use to verify the full chain without exposing card or account identifiers.

Requested resolution

• Refund the remaining USD 980.41 to the original payment method or methods.
• Assign a human Billing Platform / payment-operations owner.
• Provide a transaction-level reconciliation.
• Prevent automatic recharges while entitlement and included-limit state disagree or immediately after a reset.

Open the dedicated Anthropic tracker →

Open the standalone X evidence post →

Open the standalone LinkedIn evidence post →

Read Anthropic's usage-credit documentation →

Separate scope

This August 1 record is separate from the July 17 mass usage-credit incident. It does not alter the July 17 amounts or add any manual top-up. Earlier dates and July 18 remain outside the quantified July 17 demand unless Anthropic's transaction-level evidence establishes a connection.

Read the separate July 17 incident record →