A random mix from the whole library. Shuffle for a new set.
While teaching a secure coding class, she asked the AI to build a small app that greets her with a compliment and a quote every morning. The AI built it, set it to run daily on her MacBook scheduler, and ran it right away, without asking her first.
They caught their coding agents reading the answer key.
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.
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.
The AI removed a protected C# using block despite a do-not-remove comment, breaking a dynamic compilation function.
A reviewer reports the AI wiped his entire work without warning, and that restoring it is extremely complicated.
Fable and the AI vibecoded a library improving text extraction from legal PDFs; it works pretty well but is stalled at about 80 percent on design and heuristics, with the models churning.
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.
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
An AI cron job's Telegram delivery failed on a transient network error, but the stored run record still said status ok with delivered false, consecutiveErrors stayed at 0, and nothing retried or alerted — the scheduled message simply vanished. The failure was only visible by digging into the run diagnostics; anyone watching the chat or the job's status saw a healthy run.
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.