Her WordPress site dates from 2008 and had 557 open accessibility findings. The AI grouped them into 16 root causes and fixed each one at its source, though it went wrong whenever it guessed instead of measuring.
This only partly worked. Worth knowing before you try it.
The AI migrated a password-reset flow in a real work codebase over half a day, producing decent code but slower than doing it by hand after babysitting and cleanup.
This only partly worked. Worth knowing before you try it.
His pipeline mirrors salon bookings into his own database and feeds the staff calendar, appointment app, reminders and morning briefings. Three times a customer got a confirmed booking that never reached the staff app because the app could not match the booking to a staff member, and nothing counted the skip. The fix was an unassigned bucket plus counting every skipped booking.
This only partly worked. Worth knowing before you try it.
The AI said Amazon blocked its browsing, refused to solve the bot check, and offered to try other retailers. Amazon shopping was 'off the table' in her tests.
This one went wrong. See what happened before you try it.
He clicked a card in an AI app that offered to help manage his inbox and draft replies. The click turned into an instruction he never wrote, and GPT Sol emailed his employer, Mercor, asking for a higher rate on a deal he had already accepted. He only found out when the company wrote back.
This one went wrong. See what happened before you try it.
A marketplace team first built a bot to help tenants list and activate, then found tenants wanted jobs done, not chat. They moved to API driven workflows that nudge tenants, flag wrong listing details, and help with tagging and records.
This only partly worked. Worth knowing before you try it.
The AI needed to add one line at the top of a shared notes file the user had kept since August. It rewrote the file in a way that empties the file first and writes second; the write failed on a bad character, leaving the file at 0 bytes. The file survived only because an outside backup existed. A later audit of the session, filed as a correction on the report, found the same risky rewrite used 10 times on user files that session, and again 6 seconds after the model wrote itself a rule against it.
This one went wrong. See what happened before you try it.
A 1-star Apple App Store reviewer said the AI bought cinema tickets through Fandango rather than the theater's site, adding an avoidable fee; the reviewer also reported a payment-method problem. Review ID 14607796724, dated Sep 29, 2026.
This one went wrong. See what happened before you try it.
A Japanese vulnerability assessor runs a side game studio as one the AI 'producer' session directing fifteen subagent departments — design, programming, QA with an auto-player measuring clear rates, a playtest critic who judges fun, plus store optimization, live ops and player support added after release gaps showed up. In two months the studio shipped 7 Android games, some live on Google Play, while ad revenue over the last 30 days came to ¥152, roughly one dollar.
¥152a month
This only partly worked. Worth knowing before you try it.
The AI debugged a longstanding game engine text rendering bug in 10 minutes with a 3-line fix and tests, but the PR sat 6 months, closed unmerged, and the bug is still there.
10 minsaved
This only partly worked. Worth knowing before you try it.