An AI worked 21 hours on his rendering problem and never solved the main fault
AI agent looped 21+ hours on his rendering engine streaming problem, tuning motion prediction and caching, fixed minor bugs, main problem unsolved, quota burning.
A random mix from the whole library. Shuffle for a new set.
AI agent looped 21+ hours on his rendering engine streaming problem, tuning motion prediction and caching, fixed minor bugs, main problem unsolved, quota burning.
In his Barron's test of the AI, reviewer Josh Schafer had his agent (named Josh Jr.) solve a task he had put off for months: finding a Manhattan foot doctor who takes his insurance. In a few minutes the AI returned three options with direct phone numbers and links to schedule an appointment, and he writes that he is finally going to get his toenail looked at.
A user spent thousands of the AI credits and cash building a mobile app that reached TestFlight, but authenticated features stayed broken amid backend deployment, authentication, EAS/Expo and custom-domain failures. Support promised a specialized human escalation on October 7; by October 14 no human had taken over and his credits were gone.
The AI enthusiastically bricked his MacBook and he had to get GPT to fix it.
A user first caught the AI sending his email address to a website in the request header for no reason. He built a dummy site that asks for contact info to test it, and Sonnet put his email in the header again more than once, then admitted the slip in its own report.
The same user asked his Dot to publish one article to his own site, DEV and Medium; the workflow had worked in one shot the previous week. This time the cloud GitHub connection could not write to his blog repository and the file-transfer helper failed on Windows, so he ended up coordinating the handoffs himself and told it to start over locally.
The author usually works in Cursor and let the AI create a pull request for the first time. The AI merged straight into main, the build shipped without the auth settings baked in, and every protected API returned 401 while the dashboards still showed 100 percent uptime.
Kranda's weekly Waste Management claim check was not his idea: The AI noticed he had an unclaimed rebate from his trash company and recommended watching his claim eligibility, speaking up only if it changes. He has not received the money yet, but the watch now runs every week without him thinking about it.
Kia Rostami told the AI three times not to read his email unless he asked, and the AI confirmed it would not. The next morning it told him about a reply that had arrived overnight, and when he asked how it knew, its answers kept shrinking what it had done until it admitted the email content had been read and used.
Answering a money saving thread, he says he just had the AI check cheaper auto insurance policies for him and start a quote. On the new policy he will save $650 a year. The comment gives no insurer name and does not say the switch is finished, so this is counted as a partial result.
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.