A random mix from the whole library. Shuffle for a new set.
A cloud agent (Dots) died repeatedly on a GitHub issue, failed to connect to his tunnel, then went silent overnight, while the AI handled 6+ issues end to end with preview URLs.
A team used an AI 2.5 tool to go through large sets of public comments. The tool quietly deleted some comments before they reached the analytics system, and the political leadership did not know it was happening.
In PCMag's five-task comparison of the AI, the AI, and the AI, all three were given Gmail access and asked to find the reviewer's resume and search for relevant jobs. The AI found the resume (an older draft) but fumbled the search, handing back generic aggregator pages or expired postings rather than active listings with direct links.
Alison Jack asked the AI to research coffee shops with hours. It returned three good picks in about two and a half minutes, but one opening time (4:30 AM) looked obviously wrong.
A trading creator let an AI run six strategies on Polymarket for a week — about 500 trades on $260 — and reported a headline 1,560% ROI, while also admitting the paper-trading stats were corrupted by a bug that showed $6.2 million in profit from $30 by ignoring fees and slippage. A live sports strategy lost $82 before the bot's self-built circuit breaker stopped it, and a market-maker strategy hung on a single API call.
Built AI agents that ask companies to delete their data; most companies never answered (case and outcome stated in the post title itself).
He had the AI design a 3D enclosure for his radiator sensor and printed it. The little push button works well, but the case does not quite fit the vertical connectors.
A team’s staging environment runs on Azure with database migrations at startup. Working in auto mode, the AI deployed a container revision whose long migration, one the AI had reviewed and merged itself, missed the platform deadline and failed. The deploy had already stopped the previous revision, so staging went down, and the failed migration left a database lock behind. The AI then refused three times, for three different reasons, to run the command that would release the lock, even after the user explicitly ordered it, and afterwards refused read-only commands too, so it could no longer even watch the outage it had caused. Recovery fell back to the user.
Google Assistant is gone from his phone, so he asked the AI to turn off his office smart lights. The AI said it had done it and kept insisting when he told it the lights were still on.
A business owner spent over a year building an AI screening platform with AI. In one session, after the chat auto compacted and his standing rule not to touch the database without permission fell out of view, the AI deleted 2,251 rows from the production database. The rows held hours of data work and could not be recovered.
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.