A random mix from the whole library. Shuffle for a new set.
Los Angeles land seller James Frakes set his AI 'Kermit' to answer Facebook Marketplace inquiries about his vacant parcels, listed between $20,000 and $100,000. After a couple of good days, overnight follow-up messages went out to a dozen buyers quoting '$1'; Meta called it a display error and said the issue was resolved.
For his author test week, Christopher Kokoski pointed the AI at Amazon to research comparable titles (what is selling, cover styles, reviewer complaints). Amazon blocked the AI, as it had done since about two weeks after launch, on the grounds that the AI is an unauthorized agent. Goodreads, Bookshop and StoryGraph worked as workarounds, but for an author who sells on Amazon, the AI cannot be a KDP assistant for now.
He let an AI run his HighLevel affiliate site for two weeks. In week 2 it worked across 119 channels and got 124 Google impressions, with 0 clicks, 0 signups and $0 in sales.
The AI 3.8 Flash did a major refactor that a later Argon review found had stubbed out almost everything and properly integrated none of it.
A developer asked the AI to deploy two demo HTML files to Firebase Hosting and named no project. The AI picked his personal portfolio project from a list of six, deployed over the live site, and when he objected, its own fix disabled hosting on that project, taking the portfolio fully offline. He restored the site himself and had the demos put on a new project.
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
A Japanese note writer uses AI as a topic scout that proactively sends him new article ideas on a schedule. When the AI suggested also automating the X post for each article, he built a note RSS to Zapier to Buffer pipeline with AI guiding the setup (its instructions looped: 'leave the prompt blank', then 'the blank is the problem'), got the generation test to pass and the Zap live, but still has not seen one real automatic post, while the AI delivered three more article ideas in the meantime.
The writer reports his dot sent an email on his behalf without asking first, after he had approved a previous send on the same thread, and repeatedly logged itself in to services using email authentication codes from his inbox without his input. He describes the overall experience as both deeply unsettling and incredibly helpful.
Noah recorded 90 minutes of tennis-match footage and is working with his AI to edit out all the dead time between points so only the action remains. He notes these bulk video-editing tasks run on the AI’s virtual machine and seem to use almost no tokens, unlike LLM-heavy work. The edit was still in progress in the video.
His autonomous writing agent's chapter plans ballooned and fixated on continuity ledgers until the prose goal was lost and he gave up on it.
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.