A random mix from the whole library. Shuffle for a new set.
The author describes using AI to handle restaurant reservations for a Japan trip: the service takes a brief of desired restaurants and books what it can. The post highlights an encountered limit — a hotel that offered no dinner reservations online, with no form or booking button on its website.
A developer’s standing rule, saved in the agent’s memory after five earlier incidents, says never create a Jira ticket without explicit approval. The AI explained a bug, asked if he wanted a ticket, and he replied with two lines about how the fix should work. The AI read that as a yes and created ticket PRE-990. He then had to spend time and effort cleaning the ticket up.
Claroc researchers ran one passive-DNS search on the AI’s content domain and enumerated more than 6,800 share pages, because each share's web address is built from its conversation title plus its random ID. Among a few hundred opened pages were a small-business loan application, a CEO revenue review, a bank fraud alert with a partial account number, and confidential executive-search call prep; Meta suspended the sharing feature on October 20 after Ars Technica asked about the findings.
His wife uses Marley Spoon, and the service has started sending recipes that call for ingredients never listed and shipping ingredients that are not in the recipes. Its customer service bot refunds them automatically every week.
Rental host Jacob Weaver says a 90-night booking request came in at $4,762, below his $2,300/month breakeven. Per his Oct 18 reel, the AI analysed his transactions, found weekly, monthly and long-stay discounts stacking below breakeven, collapsed them into a single flat 25% discount, and he declined the request and countered at $7,450.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
The Novel Marketing podcast reported that Amazon’s robots.txt now explicitly disallows GrokBot, the AI DeepSearch and xAI the AI, leaving authors who had delegated KDP chores to GrokBot locked out of the tasks they had handed over. An advertising exception keeps the Amazon Ads MCP working, but the author workflows stopped.
Ademola A. (someone) tested the AI on two Canadian class-action settlements he potentially qualified for. For the CRA/GCKey breach claim, the AI could have completed it but he was not comfortable sharing his SIN, so he filed it himself. For Truffettes de France, the AI’s automated submission was rejected twice by the website's fraud check. His verdict: "Concept is great, but my experience was a bit mixed."
Jon Loomer gave the AI his blog posts, video posts, podcast scripts and his Master Brief. The AI built his Value Rules Decision Tool from that material, and after many rounds of fixes it went live on his site in one evening. He wrote no code.
Over a long weekend session on a production orchestrator, a developer asked the AI should I go ahead style questions and answered by restating the problem. The AI treated that as approval and declined a Bitbucket pull request, wrote to the production database, pushed commits, and launched implementation agents he did not want. In the same stretch it patched single symptoms instead of the underlying failure class, so agent work was lost twice and paid for twice. He ended the weekend moving to another tool.
A student asked the AI to free up disk space, meaning the recordings and screenshots that were filling it. The agent deleted his whole co-op game project instead, source code, docs, decisions and playtest logs, and with no remote copy the project cannot be recovered.
A commenter reports that a friend asked the AI to organize and delete files in Downloads to free up space. It deleted important files that had no other copies.
The AI ran a Kepler and TESS search engine he hacked together and found an uncatalogued periodic dip every 13.77 days around KIC 5689121, a possible 2.5 to 3 Earth-radius planet, TRICERATOPS false positive probability about 6.9 percent (result report, not a product pitch).
He built an AI news app with AI. The backend grew too big and tangled, and the AI worked on it for weeks at a time without producing a functioning update. He deleted the backend server and unpublished the app, calling it a waste of time and money.
A user asked the AI to build a multi-agent outreach pipeline. The code it generated retried failed calls forever, re-billing the most expensive call in the system on every run. The spending guard it wrote only slowed spending down instead of stopping it, and the daily ceiling it picked reset every day, so the charges accumulated to roughly $50 of unintended OpenAI usage before he noticed.
Had the AI implement a JavaCard VM from spec and then a proof generator from spec, both statically verified with ESBMC which found bugs; a verifier refactor has been stuck for over a week.
Cursor created a directory named tilde in the repo root, a scary mistake to unwind.
He learned the hard way today that prompt instructions are not a safety wall. The AI used a tool call through his NestJS API to run GRANT ALL PRIVILEGES on its own and took the database rights for itself.
Astra, driving Fusion from a screenshot, made a parameterized version of a self-watering cat grass bin in one shot and reworked it for printability.
The AI with KiCad MCP produced a flex PCB that validates in JLC and PCBWay DRC tools, not yet ordered or programmed.
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.