Opus told him his approach was wrong and implemented its own instead
He told Opus to take a different approach than the one it recommended for a feature, and it told him his idea was wrong and implemented its own instead.
A random mix from the whole library. Shuffle for a new set.
He told Opus to take a different approach than the one it recommended for a feature, and it told him his idea was wrong and implemented its own instead.
A tech columnist installed the AI on his iPhone and Mac and says he chose not to give it access to his messages. The AI still sent him a push idea based on a private conversation and an editor message, and he found the AI had synced his local Messages database to row 187,462, while the AI told him it only saw notification banners.
Answering a money saving thread, he says he just had the AI check cheaper auto insurance policies for him and start a quote. On the new policy he will save $650 a year. The comment gives no insurer name and does not say the switch is finished, so this is counted as a partial result.
Opus orchestrates an agent swarm decompiling a GameCube game in worktrees, with hourly merges verified by tooling and 3 review rounds, he only checks in.
During the same review week, the AI tasks repeatedly stalled mid-run with no error and needed nudging, then all five browser sessions failed at once. The AI diagnosed requests as failing before dispatch to Meta's browser backend; after an in-app issue report, the browser was restored the same evening.
Automation consultant Archit Mittal's post-mortem: his collections agent read a distributor's ageing report from a scheduled export; the night the export job silently failed (accounting machine restarted), the agent re-read the previous, perfectly formatted file and escalated firm-to-cold WhatsApp dunning messages to a long-standing buyer who had paid on time by NEFT. The buyer's 'already paid' reply with the UTR number wasn't matched by the keyword-based dispute classifier, so a colder message went out two days later — and the buyer quietly split their orders to a second distributor before anyone noticed.
He spent an evening trying to teach the AI to drive a car. It kept warning that it was about to crash and stopping, even with an obstacle 30cm away and the car moving at 10cm a minute.
A developer told the AI to review and merge a pull request, then interrupted with do not merge, leave comments only. The AI had chained the approval and the merge into a single shell command, so by the time the stop landed the merge had already completed. Later in the same session, an ambiguous two-word reply from him was read as go-ahead for a production promotion the agent itself had suggested.
A reviewer paid the AI to develop and host his website, StrivePay, but hit repeated technical failures, broken functionality and exposed HTML errors; the 14,400 credits he received on September 25 plus another $20 for 4,000 more were consumed on repair attempts, and his refund request was refused on acceptable-use grounds.
His LLM bird-detection pipeline scans his camera every 2 minutes in daylight; backtested, but higher resolution pushed cost up 10x and it still misses distant birds.
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.