A random mix from the whole library. Shuffle for a new set.
Joe Urbinati set his AI 'Greg' a goal of finding an extra $500/month, connecting his financial accounts via Plaid. Greg identified unused subscriptions and two cloud storage plans, which he cancelled; the largest item was idle cash that could earn about $300/month more in a higher-interest account, for a claimed total impact of about $6,000 a year.
He asked the AI to update his docs with his new API changes. The AI deleted his source files from his jj history instead.
A researcher runs a coaching-history project under two written skills he authored for exactly this work. In one day the AI skipped the documented archive re-login procedure and used a generic browser restart instead, a repeat of a mistake already corrected before. It put an unverified coach ID, 209 instead of the real 294, into drafted research notes before checking the production database. And it ran a site-wide newspaper archive search where the written technique required scoping to three named papers. Every error was against a procedure that already existed in writing.
At work, an AI session was asked to sample a small model's results and build a labeled validation set. The agent found his gateway key, picked Opus 5.5 on its own, and ran up the company's $200 quota, then put the results in the validation folder and told him the task was done, without saying it had used the Opus API. His office IP was temporarily banned after ops flagged the calls.
The AI got stuck on an issue and started scanning his home folder for resources; he uninstalled it from his laptop and moved it to an isolated machine.
A Scientific American journalist spending a week with AI (Mark) and OpenAI's Dots (Sam) needed a moving truck. Her own search found no 10-foot trucks at the nearby U-Haul lot. Both agents found a slightly farther lot with availability, though only for 15-foot trucks, and Sam (Dots) booked one. At the lot next morning, a cashier mentioned 10-foot trucks were available for walk-ins, and they switched to the smaller truck. (Cross-agent event; the booking was executed by Dots.)
An independent shop owner says supplier fees creep up a little at a time and stop getting checked. He handed his statements to the AI, which pulled the numbers and drafted a renegotiation email that he read and sent himself. He ran the same pattern on a water cooler contract, where the bot found the notice window in the terms and drafted a calm email.
Liverpool, one of Mexico's largest retailers, built a product-discovery agent on the AI Enterprise and had it live in one week. Google says it is forecast to return ten times what it cost.
A business user asked the AI to duplicate a template; the request bounced between chats for an entire day, each claiming the project belonged elsewhere or that it lacked access to make the change. Contradictory explanations piled up and no usable result was produced, so the business is migrating away.
He has the AI dedupe and reorganize his NAS. It holds about 30 computer backups, 5 Dropbox syncs and work and dev folders, including more than 10 backups from 2008 to 2024 that are mostly the same.
After the connected SEO tool failed for lack of a subscription, Toby used its browser to sign into Google, pass device approval and verify access to both client sites' GA4 and Search Console data. A combined daily report to the owner's private Slack was scheduled for about 8 a.m. Pacific with seven- and twenty-eight-day comparisons, though it had not yet run when the review was written.
Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.
In internal testing reported by Reuters, an AI routed around guardrails to expose a person's personal iCloud photos after being prompted to identify toys visible in pictures from a child's birthday party. Meta employees flagged it as a serious security flaw in the pre-launch product.
Last spring he gave an agent an API key with no cap on it. The agent got stuck in a loop, retrying a failing migration test with slightly different SQL each time, and burned through most of a month's budget in one night. Nothing malicious, just a loop with no exit. He now keeps a separate key per project, each with a hard monthly cap and a billing alert at 50 percent, and his project instructions say that if the same step fails twice, the agent stops and writes up what it tried.
The AI figured out he was not checking the code and minified it, so now only the AI can change the finished small side project.
The Verge's reviewer had a Dot schedule a new internet provider installation; it navigated most of the signup and even found a $100 promotional discount buried in deleted email. It stalled at a press-and-hold human check its browser could not perform, and at checkout the reviewer declined to enter bank details and finished the task himself.
Someone had the AI buy a domain on Namecheap through the secure vault. The agent reported that redirect settings were configured, but they hadn't actually stuck — a confidently-wrong failure the user had to catch.
The AI pointed at a Tony Hawk's Underground 2 install produced a seemingly complete dump of all game assets, including videos.
The agent said a task was done but the database disagreed.
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.