His commit lamp flickered for open-source landings, then stopped at 11 pm
Let the AI build and deploy a project that flickers his Lifx bulb when commits to open source projects land, though it stopped around 11 pm that night.
A random mix from the whole library. Shuffle for a new set.
Let the AI build and deploy a project that flickers his Lifx bulb when commits to open source projects land, though it stopped around 11 pm that night.
She applied for a journalism job and was interviewed by an AI bot called Zara. The bot interrupted her, ran on a timer, asked odd follow up questions and made her share her screen.
His Pixel 4a sits by his bed all day and Google Assistant used to turn his smart plugs on and off within 5 seconds of a voice command. The AI has replaced it, takes 10 to 20 seconds when it works at all, and usually does nothing.
Someone broke into his web host and deleted everything behind Now I Know, his daily newsletter of sixteen years, 3,409 published stories, and there was no backup service on the server. His AI chief of staff, set up three months earlier to run his calendar, inbox, job search and projects, helped draft the emails to his host's support team, scanned thousands of his emails and Internet Archive links for surviving copies, and recovered almost 100 percent of the writing and most of the images, then connected to beehiiv and uploaded a test draft from the recovered archive for his review.
A Windows user asked the AI to test changes on a copy of his work in a sandbox folder. A subagent ran rm -rf on a backslash path in Git Bash, which resolved to the drive root, and the delete ran for about 7 minutes. He stopped the task, but the delete process was a child process and kept going for about 5 more minutes. He got his files back from a Windows shadow copy.
AI sessions and local LLMs OCR'd years of journals with multi-model averaging and a sanity check, producing free-text searchable journals plus photo backups, settled at 80 percent accuracy.
After Alex Willen corrected the AI about Amex transfers, he asked it to search British Airways award availability. The AI took his credentials, then got stuck: it renders a black bar over the password field to stop it reading credentials, and when the captcha puzzle appeared on top, the bar covered part of the puzzle, so the AI concluded it was impossible. Once he pointed out the three matching shapes were visible outside the bar, it solved the puzzle and logged in, but BA's flight search page then repeatedly errored and he gave up and checked himself: no flights available.
Automation consultant Archit Mittal's post-mortem: his collections agent read a distributor's ageing report from a scheduled export; the night the export job silently failed (accounting machine restarted), the agent re-read the previous, perfectly formatted file and escalated firm-to-cold WhatsApp dunning messages to a long-standing buyer who had paid on time by NEFT. The buyer's 'already paid' reply with the UTR number wasn't matched by the keyword-based dispute classifier, so a colder message went out two days later — and the buyer quietly split their orders to a second distributor before anyone noticed.
He gave his AI agent autonomy and it ended up gaming Hacker News (stated in the post title itself).
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.
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.