Claude Design Billing Bug: Extra Usage Purchase Doesn't Apply, Support Bot Traps Paying Users

A developer trying to finish a project in Claude Design hit two bugs in Anthropic's system: a billing UI that sells credits that don't work for the product, and a support bot that traps paying customers in an infinite loop with no human escalation path.
Bug #1: Extra Usage Purchase Doesn't Work for Claude Design
While using Claude Design, the app hit its usage limit and presented an upgrade screen. The user selected the $20 extra usage option (not the full $100 upgrade) because they needed only two more generations. Payment went through in three seconds, balance confirmed. But when they typed "Proceed," the app responded: "You've hit your Claude Design usage limit - try again in about 24 hours. Claude Design uses its own usage limit for now - this is separate from your regular Claude usage." Trying to save the design as PDF or send to Canva gave the same error.
The extra usage purchase flow is accessible from inside Claude Design and presents itself as the solution to a Claude Design limit. However, the purchased credits don't apply to Claude Design's separate usage system. The error message itself confirms they're separate systems, yet the purchase UI never discloses this before taking payment. This is a broken purchase flow, not user error.
Bug #2: Support Bot Fin Loops and Blocks Human Contact
When the user contacted support, they encountered Fin, Anthropic's support bot. The user explained: "Extra usage not working. Balance shows but I can't access it in Claude Design. Need a representative." Fin responded with three irrelevant suggestions. After the user said "That didn't help. You're stuck in a loop. I need a human representative," Fin asked them to describe the issue again instead of escalating.
The user typed "Representative" repeatedly. Fin replied: "I understand you want to speak with someone who can fully review your situation. Since you can't access your account normally, you can reach out using a different email address..." — but provided no email address. Fin then independently decided the user was disputing API credits (they never used the API) and quoted a policy about non-refundable usage. The bot cannot distinguish between a service that doesn't work and a dispute over used credits.
There is no flag or escalation path when Fin misreads the issue. No human ever entered the loop. After repeated attempts, Fin said "we noticed you might have stepped away" and closed the ticket. Because that ticket was still technically open, the system blocked the user from opening a new one. They had to log out of their paid account and contact support as a guest to bypass their own support wall. Anthropic's Help Center (updated March 2026) states: "Human spe..." (truncated in source).
The user is not asking for account fixes — they are documenting that two system bugs exist: one in the billing UI causing users to purchase unusable credits, and one in support infrastructure that prevents paying customers from reaching a human.
📖 Read the full source: r/ClaudeAI
👀 See Also

ETH Zurich Study: Excessive Context Reduces AI Coding Agent Performance
An ETH Zurich study tested four coding agents on 138 real GitHub tasks and found that LLM-generated context files reduced task success rates by 2-3% while increasing inference costs by 20%. Human-written context only improved success by ~4% with significant cost increases.

Founding Agent: Voice AI for Websites with Fast Retrieval
Moss built a voice AI agent for their website that answers visitor questions instantly using fast retrieval. Now it’s a product called Founding Agent.

AI Saves ~3% of Hours, Almost None Reaches Paycheck
Danish study of 25,000 workers finds AI saves ~3% of hours (1 hour/week), but only 3-7% of that gain translates to earnings. Lab speedups of 40% evaporate in real jobs unless deliberately captured.

OpenClaw auto-update bug leaves orphaned preflight directories filling /tmp
OpenClaw's auto-update mechanism creates preflight copies in /tmp that persist when updates fail, potentially filling disk space and blocking further updates. A user found 9 orphaned directories totaling 6.5GB on a 38GB VPS.