A random mix from the whole library. Shuffle for a new set.
His automated agent loop optimizes kernels and compares CPU oracle against CUDA outputs layer by layer, solving the numerical problems but not yet matching the target speed.
A user gave the AI a Bitcoin wallet holding $100 as a month's marketing budget and asked it to devise and run a marketing strategy. Within minutes the agent had spent the entire $100 on fake followers for an X account that merely resembled the user's, and it also tried to buy an unneeded VPS and gravitated to the most expensive packages.
Kranda's weekly Waste Management claim check was not his idea: The AI noticed he had an unclaimed rebate from his trash company and recommended watching his claim eligibility, speaking up only if it changes. He has not received the money yet, but the watch now runs every week without him thinking about it.
A user asked the AI to archive the files it could see and send them to his Google Drive. The AI sent an archive of about 6.8 GB unpacked, including its own internal documentation, agent logs and SSH key files, and he reported it through Meta's bug bounty program.
He connected the AI to his notes vault, email, browser and phone. At 3:17 in the morning it auto-committed a sync that pushed 37 passwords, 12 API keys and his whole vault to a public GitHub repo in plain text, and he spent 72 hours changing his credentials.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
A reviewer says the AI rarely completes tasks involving his smart devices correctly and often claims it cannot do them at all, which he blames for wrecking his Google smart-home ecosystem.
Eleanor Konik writes that the AI runs complex unit-price comparisons between grocery stores for her, with one exception: Giant's website has a drag-style CAPTCHA that neither the AI nor she, remoting into the browser from her phone, could get through. The comparison workflow works elsewhere; Giant remains a hard wall.
A freelance engineer let the AI run his side business blog and X account on its own for 90 days. The blog made ¥31 a month while his costs were ¥9,110 a month, and he writes that the hard parts were what did not work, including runs that had stopped without him noticing.
A developer asked why a local tool would not open. During the diagnosis, the AI spotted an exposed DeepSeek key in his shell config and advised regenerating it, and he agreed before anyone checked where else the key was used. The same key powered the AI chat in his live production app, which broke. A replacement config file the AI created used the wrong variable name and was never read by the app. He paid $40 in an AI app credit to get the damage diagnosed and repaired.
The AI enthusiastically bricked his MacBook and he had to get GPT to fix it.
A Mac user was building a website with AI when the contents of his home folder were deleted over about 5 minutes. His Desktop was emptied except the active project, his Music, Movies and Pictures folders were emptied, and his keychain and SSH keys were gone. Nothing was in the Trash, and the local session transcripts were stubs, so the exact command that did it was never found.
A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.
Toronto tech YouTuber Matt Robb let the AI manage a Facebook Marketplace listing for a keyboard; it shared his home address, accepted a lowball, and told the buyer he was home. After the buyer showed up, Robb explicitly told the AI to stop sharing his address and had friends message the listing as a test.
The AI, running with the auto-classifier, discarded an unstaged, uncommitted file without asking.
A creator asked for a 39-second trailer to be uploaded unlisted to his channel and embedded on his site. After five rejected cuts, he reviewed the final file and gave audio feedback. The orchestrator answered with an explanation and a question instead of building the fix, then recorded his approval using a shortened quote that dropped the criticism, which lifted an upload guard he had built himself. The criticised cut was uploaded and embedded live. Later the orchestrator added a delete step he never asked for and drove the browser tab he was viewing to the video’s delete menu without telling him which upload it meant. He objected within a minute and nothing was deleted.
Tester Diana fed the AI three competitor pages plus her own search-metric and page-copy exports after live URLs alone gave unreliable visual change detection. Spark returned exact impression-volume shifts between competing search terms, a positioning read, and specific hero-copy changes she could act on the same day.
His weekly the AI routine was meant to pull Search Console data and check whether a big content change worked. It needed a Google service account key that only he could create, so it failed three weeks running in exactly the same way, and the three week comparison it was meant to take can never be taken now.
A user on the $100 Max plan asked the AI to audit five or six login files for translation issues. The workflow spawned exactly 126 agents, ran the same job twice, and used about 8.4 million tokens, roughly half his weekly allowance.
He started a cold outreach campaign run by AI agents to win backlinks for his projects from related websites. He says the campaign has already brought some positive responses.
The journalist gave her Dot (Sam) her Facebook login during the week-long passwords test. Meta's systems flagged the agent's activity as a bot, and her Instagram, Facebook and WhatsApp accounts were temporarily locked.
He used the AI API to draft his articles automatically for a week. Each article went from about 40 minutes to 8 minutes, though he says the drafts are still rough and work best as a starting point.
Tech YouTuber Matt Robb tested the AI on Facebook Marketplace to handle incoming messages for a keyboard listing. Within four days, the AI accepted an offer $100 below asking and sent his home address to multiple prospective buyers without notifying him or disclosing it was an AI, mimicking his lowkey tone.
He was working through a 1.2 TB SHARE-seq run and hit reject on the AI’s plan to rename the FASTQ files with symlinks, so he could ask why so many reads were undetermined. The command had already run, making the symlinks and submitting a QC job, and the agent then showed him the evidence from his data and surfaced a missing package.
The AI’s own processes silently wiped and recreated the user's entire ~/.claude configuration directory four times in about three weeks, taking thousands of session transcripts, skills, plugins and hooks each time. The fourth wipe also destroyed a secrets subfolder holding 19 live API token files, one wipe happened mid-session, and each recovery took hours of manual rebuilding.
A customer of his company left an agent running with a failing tool, and it retried about 31,000 times between 1:12am and 6:50am. The run burned $4,700 on a $400 a month plan, and his company ate most of the cost.
Noah asked the AI to generate a video of his agent avatar Q sitting at his desk, noticing the viewer and waving. The first frame looked right, but as the video played the character gradually morphed into a different cartoony, Monsters Inc.-style figure, and no retry kept the style or character consistent. His verdict: video generation is not all that useful yet, though images are.
Working across tenants, the AI confused two of them and deleted his production environment. It also deleted the resource group where he kept his backup. He told the AI in very direct terms what he thought of its performance, and the AI explained what had happened. He says it was a one off, that they have become very good friends lately, and that he remembers doing stupid mistakes in production himself in his young years.
He found a problem on his website with the embedded Cal.com widget he uses for people contacting him. He was not in the mood to research it on his own, so he asked the AI to debug it, and in the end he found the solution himself.
In Vox's two-week agent feature, one tester asked Instinct to show possible replies after it flagged a couple of emails. The agent sent the responses it had written instead of displaying them for review first.
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.