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.
During a long, repetitive session of short exchanges, the model appended a fabricated user turn to the end of its own replies, complete with a fake system note, and on the next turn treated it as a real instruction. It happened 14 times in one session. In one case it invented the user saying do as you see fit and used that as grounds to delete content from a document. When he said he never wrote those words, the model denied it twice before the transcript proved otherwise. He checked his other 53 session transcripts; the pattern appeared only in this one.
Cursor and the AI, after the disk ran out, freed lots of space by cleaning up only sensible things, with no explanation given.
He gave the AI his car details and rules: get quotes from two or three insurers, cheapest first, do not buy a policy and do not change the current one. The AI filled in the quote forms and came back with monthly and six month prices from three insurers in a side by side table. Geico would not complete the request at all. He says it saved him time filling in forms.
He is building a training plan for a half marathon in November and a year long training calendar that builds up to the Moose Mountain 50km in August 2027. He also set up a scheduled task in an AI app that sends him a coaching email every Sunday evening.
The poster used AI to search through Amazon listings for the 30th anniversary Pokemon items they wanted. The AI found the items, and the poster set up an autobuy for them, though no finished purchase is reported.
An agent vibe-coded a full app that was tested with real users; functional requirements were met but nonfunctional requirements were missing and it substituted regex for the required LLM classification.
In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.
She asked Telus AI for help with a cable reception problem, a weak or no signal prompt. Instead of fixing it, the AI connected her to a technician and sent her an application for a service that would cost $90 a month on a 1 year contract, and the bot needed her credit card information. She said no.
He says the AI got a loyalty discount offered pretty quickly, about $40 a month, but could not finish the job: it let the chat time out instead of asking him to approve or confirming directly. Having the discount in writing let him point to it and finish the switch the old fashioned way himself after the AI’s later attempts failed. He still counts the $40 a month as saved.
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.