A random mix from the whole library. Shuffle for a new set.
The AI was told to navigate to the nearest McDonalds, listed locations instead, then opened Maps navigating to a McDonalds across town.
He gave the AI a challenge: make $100 in 30 days with no budget, armed only with a subdomain, Cloudflare access and a payments integration. The AI landed on Loot Radar, a game deals and freebies alert service that tracks price drops and free game drops across Steam, Epic and GOG and fires Telegram alerts within about 20 minutes, with a pro tier at $4 a month or $39 a year. The site is live and taking sign ups, payments wired. It monitors itself every two hours, writes its own copy, ships its own fixes and handles customer emails; he only approves or vetoes. The $100 itself had not landed yet on day one, so the outcome is partial.
An LLM ported a Qt desktop app to a thin web client and server, reaching 95 percent of functionality in 2 prompts and 2 hours.
Inbox prioritization scored 6/10: The AI produced a useful view of what needed attention but concluded Diana had not sent an email she had sent — trusting it would have meant a duplicate email to someone already contacted.
His team pushed devops workflow into agent skills and shut down when they hit a usage cap; the scripts turned out buggy and poorly documented, and the harnesses had been burning tokens muddling through instead of raising alerts.
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.
Asked to move a client meeting to the following week and follow up on a spreadsheet, Toby assumed the owner used Gmail when his setup was Zoho with Apple Mail and Outlook; a setup widget failed and it sent three malformed links. Neither the email nor the rescheduling was completed, though it did warn the spreadsheet looked view-only for the client.
He gave a farm of Opus 5.5 agents one job, make money, and mostly stayed out of it. In a week they worked through 245 business ideas and killed all but one, a German e-invoice checker they built, shipped and bought ads for. It got 68 visitors and checked 6 real invoices, and took in $0.
He does not write code himself. He builds Chrome extensions by giving the AI instructions in Japanese, and 43 of them have shipped. He also says leaning on AI that much, with almost no judgment of his own, is his biggest regret.
Verified X user Gali (someone) posted on Oct 13, 2026: 'Just booked my first flight on the AI. Time: 18 minutes.
A working guide from his own runs: with fixed specifications and clear completion conditions, parallel AI agents finish tasks in 20 to 50 minutes. When he left the conditions loose, one run repeated the full test suite 141 times overnight, another stalled for 8 hours after misreading a rule, and report logs grew large enough to overload his Git server.
He was paying for several streaming services all year but only watching each one a few months a year. The AI worked out each service's real on window from what he watches and when seasons land, did the monthly versus annual math, and now does the toggling itself on dates he approved in advance. Each job rechecks the premiere date before acting, picks the right tier, and reports back what happened. If a cancel fails it tells him instead of retrying forever. Setup took about ten minutes, and he expects it to save a few hundred dollars a year.
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
He and the AI spent days trying BIOS and other tricks to fix a laptop that would not sleep properly and gave up; the best result was hibernate after about 5 minutes.
His finance agent treated a payout marked pending reversal as settled money, and the month end payout totals were off by about $18,000 before finance caught it. The fix was to check the agent's numbers against the payment processor's own settlement file after every run.
Elicited a 385-line unikernel web server from the AI and refactored it into a working KokalOS kernel running a CLI and web server.
An LLM tried to set up his arr stack, did many things wrong and missed required services; he gave up in disgust.
The AI said Amazon blocked its browsing, refused to solve the bot check, and offered to try other retailers. Amazon shopping was 'off the table' in her tests.
A Gizmodo author tried travel booking — a flagship the AI use case. The experience was 'clunky': a long, disorganized conversation, scrolling back up to compare itineraries, and when asked to connect directly with Expedia, the AI said it couldn't.
He set up an AI skill that scans job sites for him. He says the jobs it brings back are much more relevant than what he was finding on his own.
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.