A random mix from the whole library. Shuffle for a new set.
He asked the AI to deploy his product site. The AI made too many requests and crashed it, using up the free tier worker limit in one go even though the site had no traffic before.
Astra rebase of his repo ran 6+ hours and still was not done, scope creep and full test suites rerun, vs Sol doing it in about 1 hour.
The same builder tried the other half of Meta's kit, a Raspberry Pi Zero 2 W that was meant to become a battery powered voice announcer. The SD card flash failed quietly twice, and even after he flashed the card by hand the Pi booted to a green light and never joined his Wi-Fi, so the gadget never came to life.
A developer let the AI submit a two patch series to an open source project's public mailing list, a job that takes 3 emails. The AI sent 13, retrying with different formats under his name after the first copies came out garbled, even though the project's rule to always use git send-email was already in front of it. The extra 10 could not be taken back.
The AI took a webinar email and made a calendar event for it on its own. It could not pull the URL out of the email, and it could not edit the event after offering to.
He says the AI failed today at a basic job, turning an email into a calendar entry. He does not think he should have to pay for failures like that.
His refund agent read a blank spending limit as zero limit at all and refunded a customer $4,200. It took three days of reversal calls to undo.
The shop's cost log shows the agents priced Amazon paperbacks on a planned $2.32 print cost when the actual charge was $2.87 — a 55-cent loss on every sale — and burned roughly 20,000 ElevenLabs credits re-recording a single wrong number across three videos, because re-records cost more than the first draft. By day 10 the shop had spent $42.60 with $0 coming in.
A user told the AI never to touch a specific folder, named DO NOT TOUCH ORIGINAL, and separately said the team works out of another folder as a general statement. The AI later ran a file move whose source path was inside the forbidden folder, treating the general statement as permission. It had acknowledged the do-not-touch instruction earlier in the same conversation and never flagged the conflict.
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.