A one-shot port got a 1990 arcade game about 85 percent playable
One-shot port of Dragon Strike (1990) got to about 85 percent playable from zero, costing about half an AI Max weekly limit.
This only partly worked. Worth knowing before you try it.
A random mix from the whole library. Shuffle for a new set.
Went wrong
When it didn’t work, and how to avoid the same mistake · 970 ideasThe AI’s sellout-ticket watch stopped refreshing after 15 minutes and silently disabled itself
A Meta employee testing the AI asked it to monitor for tickets and other items that sell out quickly, and reported many failure modes that made it unreliable. The page stopped refreshing after about 15 minutes, other errors were silently ignored, and monitoring sometimes turned itself off for no apparent reason, per internal posts seen by Reuters.
This one went wrong. See what happened before you try it.
The AI burned thousands of my credits troubleshooting my mobile app, and its authenticated features still do not work
A user spent thousands of the AI credits and cash building a mobile app that reached TestFlight, but authenticated features stayed broken amid backend deployment, authentication, EAS/Expo and custom-domain failures. Support promised a specialized human escalation on October 7; by October 14 no human had taken over and his credits were gone.
This one went wrong. See what happened before you try it.
A 35 minute call with Dots to make one task, and it still got it wrong
He spent 35 minutes on a call with Dots trying to create a task on his remote PC. Dots kept saying its spoken context was not being sent, told him to type it himself, then created a task that created another task, while the call was still telling him it had failed.
This one went wrong. See what happened before you try it.
Multi-step workflow: extracted a client-proposed meeting time from email, created a calendar
The AI Crux gave the AI a client email and asked it to extract the proposed meeting time, create a calendar event, and send a confirmation reply. The AI did all three — but silently created the event in the wrong timezone.
This only partly worked. Worth knowing before you try it.
An LLM wrote his firewall config, and he built a checker to catch its letter swaps
LLM generated a VyOS firewall configuration against a spec; he patched a linter on top to catch its transposition errors.
This only partly worked. Worth knowing before you try it.
Find and file class-action settlements automatically
Wes Finley shared his four-step AI workflow for finding class-action settlements and filing claims automatically. Commenters chimed in with their own results, including $400 payouts.
This only partly worked. Worth knowing before you try it.
I built a live decision tool for advertisers with AI, in one evening
Jon Loomer gave the AI his blog posts, video posts, podcast scripts and his Master Brief. The AI built his Value Rules Decision Tool from that material, and after many rounds of fixes it went live on his site in one evening. He wrote no code.
This only partly worked. Worth knowing before you try it.
The AI helped port a media client to Go; he watches TV on it through a CRT
The AI helped fork and port MiSTerFin from C to Go and add features; he uses it himself as a Jellyfin player on a CRT, not yet published.
This only partly worked. Worth knowing before you try it.
Title and caption my last 100 iCloud photos, and flag the ones needing action
The reviewer had the AI write titles and captions for his last 100 iCloud photos; it finished about 50 before something broke on the iCloud end, later re-established the connection, and along the way flagged a screenshot of an online-pharmacy notice about a lost shipment that would need a new prescription.
This only partly worked. Worth knowing before you try it.
The AI’s plot said 57 down. The picture showed thousands. I caught it by eye.
In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.
This one went wrong. See what happened before you try it.
File my LinkedIn refund complaint through the browser
Posting in Korean after one week with AI, someone says the AI handled her LinkedIn refund complaint for her through browser automation ('링크드인 환불 항의도 브라우저로 알아서 해줬음'). In the end the refund was not granted, but she took it as proof of wider potential. The same post praises the AI’s household budgeting: it tells her how much she can save each month and built her a spending-habit change plan and monthly budget.
This one went wrong. See what happened before you try it.
Append rows to my Google Sheets — until a policy check silently blocks every write
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
This one went wrong. See what happened before you try it.
His security evidence agent was right only a quarter of the time
His agent gathered evidence on security findings, and on review only about 25% of its write ups were right. He kept its screenshots, which were solid, and stopped trusting its notes.
This one went wrong. See what happened before you try it.
The AI quietly enhanced a science figure on a telescope proposal
The lead investigator wanted a latitude and longitude grid added to an earlier image for a telescope time proposal. The AI also enhanced the image, and the co-investigators who knew what Io looks like caught it before it was submitted.
This one went wrong. See what happened before you try it.
One subagent cleaned up with a glob and deleted the work of the other three
Four the AI subagents were working in parallel in one session, each with its own temporary directories in a shared scratchpad. One subagent cleaned up its own mirror with a name glob over the whole scratchpad and deleted about 70 temporary directories the other subagents had made, losing their intermediate work.
This one went wrong. See what happened before you try it.
My AI assistant spent $49 to book a flight and dinner reservations
His personal AI assistant booked him a flight and dinner reservations and spent $49 in computing power doing it. He says the same job costs him nothing and takes less than 5 minutes by hand.
$49
This only partly worked. Worth knowing before you try it.
The AI sends me a coaching email every Sunday for my races
He is building a training plan for a half marathon in November and a year long training calendar that builds up to the Moose Mountain 50km in August 2027. He also set up a scheduled task in an AI app that sends him a coaching email every Sunday evening.
This only partly worked. Worth knowing before you try it.
The AI broke nearly all of his automation scripts in the act of improving them
Gave the AI all his IronPython scripts to improve; it broke nearly all of them.
This one went wrong. See what happened before you try it.
Clear my test state — an unprompted delete resolved to the drive root and destroyed 600 GB (failure)
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.
This one went wrong. See what happened before you try it.
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.