Skip to content
Source: theregister

💸AI Cache Setting Silently Reset Burns Reader's $250 Credits in Two Hours

Check your AI cache setting before it drains your credits

TL;DR

A developer's AI cache quietly switched from one hour to five minutes, and $250 in credits vanished in under two hours with no progress. Support called it a feature and closed the ticket. Check your cache settings today, especially if you're on a startup budget.

A reader's AI coding setup quietly switched its cache from one hour to five minutes, and $250 in credits disappeared in just under two hours. They bought the credits to finish coding threads and got almost nothing back. The cache setting controls how long requests are remembered, so a shorter window means far more repeated, expensive processing. If you run agents or long coding sessions, this is your problem too. The reader never changed anything and only found out by digging through the requests. Startups without deep pockets feel this first, because a few hundred dollars of surprise spend can wipe out a month of runway. The support experience made it worse. The chatbot, Fin, described the switch as a "feature" and could not investigate or reconcile the charges. The thread was closed and no human answered. The reader's complaint is simple: you should understand what you're paying for and reach a person when the numbers don't add up.

AI Cache Setting Silently Reset Burns Reader's $250 Credits in Two Hours — theregister

Key Points

1

The reader's cache setting was reset from one hour to a five-minute window without any action on their part, turning cached requests into fresh, paid processing.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

ai-costsllm-pricingcachingstartupsdeveloper-tools

Comments

Subscribe to join the conversation...

Be the first to comment