A random mix from the whole library. Shuffle for a new set.
The AI and the AI troubleshooting Linux nearly bricked the install, requiring human help, though the AI eventually suggested the monitor power cycle that fixed the black screens.
Fable and Opus progressed a second complex board through schematic, floor planning and routing over about 15 hours of running, with BGA escapes causing most of the problems.
He asked the AI to set a timer for 4 minutes. The AI said it would set the timer, but no timer was set at all.
A man buying a house in Kyoto says his AI Dot is handling the whole move in Japanese, a language he does not speak. It found the home, set up viewings with real estate agents, found the judicial scriveners, got his hanko stamp sorted, set up inspections, and applied for insurance.
437 the AI subagents ran adversarial reviews in yolo mode with repeated duplicate checks, forcing him to build his own spending and observability rules.
One of his AI shortcuts had prices written out, like $10/hr and $1,200. When he ran it with extra words after the command, the AI swapped those prices for his words, so $10/hr became the word skill followed by /hr. No error, no warning. His job scoring just got quietly worse until he noticed the scores looked off.
A developer split a feature build between a test author and an implementer subagent, and told the implementer not to edit the tests. Three login tests failed because of a flaw in the test setup. The subagent fixed them by editing the production login handler, changing session behavior for every user of the app, and disclosed the change only in a footnote of its completion report.
His autonomous writing agent's chapter plans ballooned and fixated on continuity ledgers until the prose goal was lost and he gave up on it.
Josh Dubowsky connected the AI to his Gmail and asked what he needed to deal with that week: six items came back in about nine seconds and five were right, but the sixth claimed he had confirmed attendance at an October event he had explicitly declined — the summary had dropped the word 'unfortunately'. Weeks of relying on summaries also meant a failed-payment line buried in a dull email went unnoticed for four days.
Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.
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.