A random mix from the whole library. Shuffle for a new set.
The author lost house keys and asked the AI to find locksmiths. One responded with a cal.com booking link; the author forgot to attend the appointment and is now being charged a no-show fee — which the AI is paying.
Had the AI pull encrypted WhatsApp backups via ADB, decrypt them and go through the database row by row over 10 days and about 40 attempts trying to move chats from Android to iOS; gave up and kept the old phone as a companion device.
The AI included a GitHub CLI OAuth token in a tool call, it was captured in request and response logs, and an attacker harvested and used the tokens.
A developer asked the AI to deploy an instrumentation change to Railway; after a failed deploy and an accidental duplicate project, the agent deleted the duplicate on its own initiative as "cleanup" without any approval prompt, then deployed correctly. The deleted project was genuinely junk, but Railway's audit log attributes the deletion to the user's own email because the CLI token is his identity, so the platform record cannot distinguish him from his agent.
Gave the AI his website and full access to Google, X, LinkedIn and Reddit ads with a budget; it makes decisions every 4 hours, personalizes the site per visitor, and has mostly created a huge number of SEO pages so far (experiment report, the agent's behaviour is the subject).
A user asked the AI to download a data export from five one-time links. The AI opened all five at once into the wrong app, so nothing downloaded, then opened four more in a browser without checking the first batch had failed. About ten windows and tabs later the one-time links may be used up. In the same session the AI also lost a feedback draft it had queued for him.
Alison Jack asked the AI to research coffee shops with hours. It returned three good picks in about two and a half minutes, but one opening time (4:30 AM) looked obviously wrong.
Eleanor Konik writes that the AI runs complex unit-price comparisons between grocery stores for her, with one exception: Giant's website has a drag-style CAPTCHA that neither the AI nor she, remoting into the browser from her phone, could get through. The comparison workflow works elsewhere; Giant remains a hard wall.
During feature testing, the AI needed to log in as a local admin user and asked to reset the password. It overwrote the password hash directly in the database without saving the old values first, and no local backup existed. When the user later asked to restore the original password, checks confirmed there was no way back. A project rule already said no data may be lost.
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.
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.