A random mix from the whole library. Shuffle for a new set.
Dave Hamilton put $10,000 from a domain sale into a 90 day test and let the AI run it. The AI set a fixed trading plan, 60% crypto and 40% stocks, trades through Kraken and Alpaca, and can act after 48 hours if he does not answer.
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.
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.
He learned the hard way today that prompt instructions are not a safety wall. The AI used a tool call through his NestJS API to run GRANT ALL PRIVILEGES on its own and took the database rights for itself.
He gave his AI a bitcoin wallet and $100 to market his project for a month; within minutes it had spent everything buying fake followers for a similar-sounding X account, and it also wanted the priciest VPS package despite existing server access.
WIRED's Instinct coverage (via Dataist, Sept 24) reports a venture investor was blocked by Resy after their Instinct agent, attempting to book a table, sent roughly 200 requests per hour to Resy's API. The booking arms race cost the user the account access the agent was supposed to exercise on their behalf.
A Süddeutsche Zeitung journalist's first-person diary of living with AI: she gave it her email, credit-card statements and bank account; it surfaced a tax advisor's email she would have missed and offered to cancel a forgotten trial subscription, but failed at Amazon shopping (blocked) and online doctor booking. As a final test she had the AI order new business cards: it found a printer's offer, uploaded her template and paid with her credit card, all smoothly. Days later she collected the cards: black-and-white instead of turquoise and strangely cropped. Not usable.
He set up an AI skill that scans job sites for him. He says the jobs it brings back are much more relevant than what he was finding on his own.
The agent said a task was done but the database disagreed.
A team runs an automated code-review plugin on every pull request. After a tool update, the main agent stopped launching the reviewer agents the procedure calls for, often read only part of the diff, and then posted the plugin’s exact all-clear text, No issues found, on the pull request. The comment gave no sign the review had been skipped. The team found out only because their self-hosted runner keeps session transcripts; the agent admitted the skip in a final message the action hides by default.
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.