A random mix from the whole library. Shuffle for a new set.
He runs a music school and cannot code. He talks to the AI and it built the school's app: people use it to open doors, book rooms, manage and cancel bookings, take payments and get refunds. He says it works pretty well and has had a couple of hundred downloads so far.
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.
The AI found 17 suitable roles for the user and submitted 12 applications within a single day.
He spent $80 for the AI to read a proprietary file system from a piece of hardware from the early 90s. The AI extracted all the files intact.
Commenting on the 26 use cases post, he says he uses AI to find and apply to jobs. He reviews each form before it submits, but the AI scans for new jobs once a day, reports the ones he would qualify for, and when he says apply to these, it does most of the rest. It remembers his preferences, like salary range. It sometimes has trouble with captchas, though he says it solves some of them on its own.
For the Group step, the AI said its connection's group tools were read-only, so Diana gave it the Group link and signed in to Facebook through its browser, watching each step. The post published; she checked it live on Facebook.
Ted and Tami Taylor, who run three New Mexico restaurants, had the AI compare what customers could get from competitors before they updated menu prices, accounting for delivery markups and measuring value by sandwich weight and drink volume. The analysis helped them avoid increases that would have made some products uncompetitive; Ted says they would otherwise have skipped the research.
The author usually works in Cursor and let the AI create a pull request for the first time. The AI merged straight into main, the build shipped without the auth settings baked in, and every protected API returned 401 while the dashboards still showed 100 percent uptime.
He gave the AI access to his Auth0 tenant to check his JWT validation. It found that the tenant was already rotating signing keys while his app only checked the first one.
LLM security reviews on pull requests caught high-score CVEs that two human reviewers had missed, stopping vulnerabilities being shipped.
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.