A random mix from the whole library. Shuffle for a new set.
His scheduled the AI task crawled job boards against his criteria each morning, but every run started with no memory of the last one, so it proudly sent the same five listings for two weeks. He fixed it by giving the task an outside memory that saves what it found, what it sent and what he rejected, and the repeat reports stopped.
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.
Bryan gave the AI a basic errand: find a USB-A to USB micro Type B cable. Amazon blocked it outright, Monoprice sits behind Cloudflare so the AI could not even see pricing, and Best Buy and Walmart threw constant bot blockers (he told the AI to solve the puzzles itself, and it got past some). Checkout was its own ordeal of account credentials and a Stripe wallet; he finally spotted the item sitting in his Walmart cart in the iPhone app and completed the purchase from a third-party seller himself. His verdict: kind of terrible at basic finding and buying.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
He has the AI check his email every day for a message from Shipaton telling him to book a flight. He is still waiting for that email to land.
The Foundry team's post-mortem of running short-form posting for a debate app through coding agents driving 9 real iPhones and 44 accounts (1,506 posts since Aug 21): surprise modals — rate-this-app prompts, feature cards, iOS update nags — stalled a phone for the rest of the day (worst day: 21 missed posts), and the first version counted a post when it tapped Share, so silent upload failures and saved drafts were logged as published. Fixes were screenshot-based modal clearing, per-platform post verification and receipts so retries never double-post.
Cursor created a directory named tilde in the repo root, a scary mistake to unwind.
AI agent, asked to archive the session filesystem and send it to Google Drive, sent a 6.8 GB archive containing internal docs, code and records.
He spent 35 minutes on a call with Dots trying to create a task on his remote PC. Dots kept saying its spoken context was not being sent, told him to type it himself, then created a task that created another task, while the call was still telling him it had failed.
The AI made a bad MCP call and wiped the contents of a Confluence draft he had open in his browser. He lost two hours of work.
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.