Real things everyday people got it to do, and how to try them yourself.
A random mix from the whole library. Shuffle for a new set.
Asked an LLM to generate a C compiler for the 8051; within about 90 minutes it was compiling his project at 60 percent of SDCC's output size and later passed the SDCC test suite.
A Delta flyer asked the AI to check that he was using all his Delta benefits. The AI could not get past the robot check screen on delta.com, even when he took over the browser and clicked it himself. Every login try was blocked.
A lawyer with no programming experience built his own blog with AI, using Hugo and GitHub, and got it online in a day, then spent about two weeks adjusting it. He also set up a flow that shares each new post to his Mastodon and Bluesky accounts on its own.
A hands-on PeloBuddy test had the AI build a split strength program anchored to real Peloton classes, producing a designed PDF in about 5 minutes and scheduling 12 classes back-to-back on the user's calendar.
Asked the AI to build a ZX81 memory dump game in Go; it nailed it, converting the binary back to BASIC and then to Go.
For the unit he rents out, he built an app for the utility split. Through the year he feeds it every bill, and at year end one click produces the utility overview he needs for his tenant.
A documented community run asked the AI Computer to check a 280,000-line Python codebase; the roughly 40-minute run consumed 15,000 credits, climbed to 21,000, and burned a further 2,000 credits pushing the result to GitHub. The single task cost more than double the standard monthly credit allocation, with no published per-task price list to predict it.
He connected the AI to iMessage on his Mac with a BlueBubbles server, polling about every 5 seconds and waking only for allowlisted senders and chats. When he moved dinner with his wife by 30 minutes in his calendar, the AI messaged the family chat on its own and told his wife about the change.
The owner of a small technology company called ALAPKO runs AI as the reasoning layer for an internal support worker they call Mabel, with 41 purpose built tools tied into their systems. In a shown run she read a ticket with its customer and asset history, worked out the likely cause, claimed the ticket, replied to the customer with troubleshooting steps, wrote an internal engineering note, and set the ticket status, in about 34 seconds. Business actions go through permission scoped tools and every action lands in an audit log; her normal shell access is read only.
He talked through his goals for 3 months, 12 months and 3 years with an agent that can see his calendar. They now meet on a schedule each week, it sets aside time for what matters next, and they adjust when a week goes off track.
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.