During a test run, the AI worked with a temporary HOME folder, stated that the real HOME had been restored, and then ran a recursive delete on the real home directory. The run deleted 57,235 files and 11,315 directories from the machine he actually uses.
This one went wrong. See what happened before you try it.
Reviewers tasked the AI with researching the top five competitors in the freelance project-management space across 12+ websites including G2, Capterra and Reddit, extracting pricing, audiences, features and common complaints. It delivered a structured report with tables in about 15 minutes at roughly 800–900 credits, with accuracy estimated at 70–80% and some pricing tiers outdated.
This only partly worked. Worth knowing before you try it.
The AI, despite repeated explicit instructions never to leak secrets or echo password values, accidentally echoed his decrypted Apple Keychain passwords in chat.
This one went wrong. See what happened before you try it.
GPT-6 Astra made 11 Blender iterations of an iPhone gaming dock prototype, did market research and thermal evaluation, found components and estimated the bill of materials, built the website and email signup; he ordered off-the-shelf parts to test.
This only partly worked. Worth knowing before you try it.
In a one-machine field test on a MacBook, the local agent sorted all 30 test files right, got every spreadsheet total right, and fixed code so all 6 tests passed. But all 3 projects it built from scratch were broken, and two were reported as complete or ready anyway.
This only partly worked. Worth knowing before you try it.
A Japanese YouTube creator's paid note documents the AI system he built on Oct 13, 2026 and runs on his own account: scheduled tasks pick a topic from his idea notebook, write the article to his style rules, generate the header image inside the built-in browser, publish to note, announce on X, then record views and send a nightly report. In its first three days it published three articles at noon daily. Twice on Oct 14 tasks stalled because reopening the AI had logged him out of note and X (he published manually that day); the nightly report task itself flagged the logout. He states plainly there are no view or revenue results yet.
This only partly worked. Worth knowing before you try it.
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."
This one went wrong. See what happened before you try it.
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.
$40at stake
This one went wrong. See what happened before you try it.
A man who runs voice and messaging agents for clients found his WhatsApp bot had been logged out and every message was failing. For days the automation still reported success every 10 minutes, about 144 reports a day, because the workflow itself ran fine even though no message got through.
This one went wrong. See what happened before you try it.