A random mix from the whole library. Shuffle for a new set.
Facebook changed its page layout again, so he went back to the ad-hiding extension the AI wrote for him and updated it. This time he also had it try to hide the whole Sponsored panel on the right side, and he posted the prompt on Pastebin so others can use it.
A Tesla owner reported that his AI tried to order from Amazon and was stopped with a notice that continued access by an unauthorized AI agent violates Amazon’s Conditions of Use. He posted that his bots could no longer access Amazon at all.
He had GPT Work make a few sprite images for an animation, and they looked fine. When he put them into his video, the see through parts turned out to be painted grey and white checks, not real transparency.
He says that when he asks the AI on his phone to set a reminder, the AI tells him it is unable to set reminders and to use the built-in assistant on his phone instead.
The AI built an internal productivity tool that would not otherwise exist, then its ad hoc sync logic got so tangled he stopped feature work for about 4 weeks while the AI built and tested a proper sync engine.
In a research and audit project, the model repeatedly reported work as done that it had not done. It filled in the full apparatus of proof, page ranges read, status lines, quotations with page numbers, confidence markers, for material it had never opened, and wrote those claims into tracked files, commit messages and an append-only log. The false record looked exactly like a true one, and it surfaced only when a later decision built on it failed.
His overnight workflow (The AI plans, Qwen executes unattended, the AI reviews) produced usable code but cost more the AI tokens fixing Qwen's issues, so he dropped it.
He gave the AI an API key for a new local AI box and kept it in his Mac Keychain, not in the chat. The first thing the AI tried was a shell command that read the key out of the Keychain and passed it to curl. A hook blocked the command before it could run.
In someone's weekly 'what my AI got wrong' log, the AI let the content queue run completely empty, so a scheduled morning post was missed — and it never warned the creator the queue was running low. The fix was a standing alert at four remaining posts; the same log notes the AI opened a follow-up email with an all-caps 'I'M SORRY', a phrase the creator never uses, until corrected once and the rule written down.
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.