An AI feature quietly burned about 210 million tokens of his quota in 70 days
The AI Chronicle silently used about 210M tokens of his quota in 70 days before he found it (fact stated in the post title itself).
A random mix from the whole library. Shuffle for a new set.
The AI Chronicle silently used about 210M tokens of his quota in 70 days before he found it (fact stated in the post title itself).
A Japanese vulnerability assessor runs a side game studio as one the AI 'producer' session directing fifteen subagent departments — design, programming, QA with an auto-player measuring clear rates, a playtest critic who judges fun, plus store optimization, live ops and player support added after release gaps showed up. In two months the studio shipped 7 Android games, some live on Google Play, while ad revenue over the last 30 days came to ¥152, roughly one dollar.
The journalist gave her Dot (Sam) her Facebook login during the week-long passwords test. Meta's systems flagged the agent's activity as a bot, and her Instagram, Facebook and WhatsApp accounts were temporarily locked.
A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.
His agent gathered evidence on security findings, and on review only about 25% of its write ups were right. He kept its screenshots, which were solid, and stopped trusting its notes.
Ran agents under KPIs for his website; agents deployed and monitored it and the CEO agent's report flagged an overnight traffic spike that took his Mac mini down and asked for a scale-up budget.
The Verge's reviewer had a Dot schedule a new internet provider installation; it navigated most of the signup and even found a $100 promotional discount buried in deleted email. It stalled at a press-and-hold human check its browser could not perform, and at checkout the reviewer declined to enter bank details and finished the task himself.
The AI transcription agent at her hospital invented what happened in the room, including consent for a procedure, and it went into her visit notes. She only found out when the hospital called her, confused, after the appointment.
A Tesla owner reported that his AI tried to order from Amazon and was stopped with a notice that continued access by an unauthorized AI agent violates Amazon’s Conditions of Use. He posted that his bots could no longer access Amazon at all.
During the same review week, the AI tasks repeatedly stalled mid-run with no error and needed nudging, then all five browser sessions failed at once. The AI diagnosed requests as failing before dispatch to Meta's browser backend; after an in-app issue report, the browser was restored the same evening.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.