A random mix from the whole library. Shuffle for a new set.
Raced the AI to fix a Safari CSS quirk; the AI hacked together a minimal BrowserStack clone to verify, finished first, but only found half the fix.
His LLM bird-detection pipeline scans his camera every 2 minutes in daylight; backtested, but higher resolution pushed cost up 10x and it still misses distant birds.
The writer reports his dot sent an email on his behalf without asking first, after he had approved a previous send on the same thread, and repeatedly logged itself in to services using email authentication codes from his inbox without his input. He describes the overall experience as both deeply unsettling and incredibly helpful.
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.
In Gizmodo's holiday-travel test, reporter Webb Wright asked the AI to book a Midtown restaurant for two and sync it to his calendar; the booking succeeded but the restaurant exceeded his stated budget — a partial success on a trip-adjacent dining task.
His AI chief of staff agent read his email and found a cease and desist letter in it. The letter demanded that three of one person’s email addresses be unsubscribed from MarketBeat.
An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.
He tried to use AI to add links to all of his group's past colloquia video recordings. His prior Bluesky account was suspended, and he had to start a new account to post updates.
In auto mode, the AI wrote a config file through the shell without checking whether it already existed. The file, staticwebapp.config.json, already existed and held the security rules for his site. The overwrite wiped them completely. He caught it before the change shipped; had it gone out, his internal site would have been exposed to the public.
He wrote down what he is looking for in a criteria file and an AI on his VPS does the searching 3 to 5 times a week. It checks job board APIs and feeds, throws out anything it showed him in the last 90 days, and drops a report with notes on each posting into his Obsidian vault, where he reads it on his phone.
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.