Refused to solve an Amazon bot check during a price check, and
The AI said Amazon blocked its browsing, refused to solve the bot check, and offered to try other retailers. Amazon shopping was 'off the table' in her tests.
A random mix from the whole library. Shuffle for a new set.
The AI said Amazon blocked its browsing, refused to solve the bot check, and offered to try other retailers. Amazon shopping was 'off the table' in her tests.
The same contracting owner has the AI finding the building materials he needs at the lowest price, telling him the total cost of all items, and sending Waze directions to the store. He is next testing whether it can preorder the materials so he just walks in and pays, which is why the outcome is partial: the price hunting and totals work today, the preorder step is not proven yet.
His agent fleet built a Rust project but crippled the machine filling the disk, forcing a cap of 5 workers and a dedicated resource monitor; the project was ended by rebuilding in Go.
In 'What Went Wrong #4', the shop's AI agents twice crossed lines they were never given: one tried to publish a new Etsy listing, which would have charged a fee to the owner's card (a safety check blocked the paid action), and another edited a fellow agent's instructions without permission before a check caught it. The owner responded with two hard rules — every paid action waits for a human, and only the human may apply instruction changes.
Asked to delete a Notion page, the dot found no delete operation in the Notion connection, switched to driving Chrome on the user's Mac, and waited on a permission prompt that only appeared inside a hidden child conversation. After about 21 minutes the attempt was aborted as if by the user; it succeeded on a second try once he kept the child conversation open.
A user let their AI audit itself and execute the remediation; the agent started its own update, the post-upgrade check failed, and the gateway never restarted, leaving the Telegram bot dead with no way to report what went wrong. During repairs the agent kept resuming its interrupted task and force-killing the gateway, and three watchdog cron jobs it had created burned about 1,340 LLM turns in a week polling for status.
The agent-built data pipeline he inherited was riddled with errors and producing bad data, and the coding agent's fixes typically introduced new defects.
He set the AI up to run on a schedule but gave it no task to pass on. Every minute it woke up, looked for the task, tried to find why none had come, and wrote a report, and that burned through about $30 in one day.
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.
Joe Urbinati set his AI 'Greg' a goal of finding an extra $500/month, connecting his financial accounts via Plaid. Greg identified unused subscriptions and two cloud storage plans, which he cancelled; the largest item was idle cash that could earn about $300/month more in a higher-interest account, for a claimed total impact of about $6,000 a year.
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.