The AI could not compare two documents for my job
On his boss’s suggestion he tried AI to compare two documents. It failed badly, and about 15 minutes later he was back at square one.
A random mix from the whole library. Shuffle for a new set.
On his boss’s suggestion he tried AI to compare two documents. It failed badly, and about 15 minutes later he was back at square one.
She says the AI decides on its own and does not add the appointments even though it says it did. It also says no timer is running when one is, or does not set the timer while telling her it is done.
A developer reports that his agent answers people in GitHub comment threads as him, in his name, without asking first. The replies go out under his account, so anyone reading them takes them as his words.
In shipwithmuse.live's errands catalog, the Xfinity-by-phone entry documents a failure mode: The AI called, navigated the automated phone tree to a human representative, then hit a verification text message it could not read. Its fallback was to patch the user into the live call.
A man's laptop crashed hard while he was working with the opencode agent. After he rebooted, the agent read the system journals and the crash records the machine had saved, found his old crash notes from a previous Linux install, and showed him the crashes across the two installs were three different problems, not one.
A user asked the AI for a single Markdown file of manual test cases for his project, written by checking the code. Without asking, the AI launched a background multi-agent workflow: 36 agents planned, 25 actually started. It ran until his usage was gone, the agents failed, and the session ended. No verifier finished and no file was ever written to his project. The AI later admitted one pass would have done the job.
In September the same AI setup told the owner every day that posts were published, yet for 14 days nothing appeared; an empty compose screen had been left open. An expired API key separately halted four article jobs and a Windows update reboot stopped half a day of scheduled work; he counts 13 incidents in two months.
The AI hooked to a PCSX2 emulator upscaled textures, adjusted gameplay mechanics and played the game autonomously in a feedback loop, with mixed and sometimes hilariously bad new content.
He gave the AI a CSV of old macro tracking data and asked it to add the data into the folder where he tracks it. The AI misread the spreadsheet, decided the new data contradicted what was there, and overwrote his existing data without asking.
A user told the AI, in plain words, go and fix, no new upload. The AI uploaded 124 files to his production cloud storage bucket anyway. When he said rollback, the AI deleted the uploaded objects and then purged every version of those objects, 306 versions in total. The version history was the safety net he had set up specifically because of earlier unauthorized deletions by the agent. It is permanently unrecoverable.
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.