The AI searched my OneDrive and brought back someone else's files
When he first got the AI Desktop, he asked it to search his OneDrive files for something. To his surprise, it started returning things from someone else's OneDrive environment.
A random mix from the whole library. Shuffle for a new set.
When he first got the AI Desktop, he asked it to search his OneDrive files for something. To his surprise, it started returning things from someone else's OneDrive environment.
He is recovering his 15 year old tweets with photos that he thought were basically lost, with AI's help. The AI also built him a custom GUI editor that he will use once to hand edit the collections of tweets.
AI agent, asked to archive the session filesystem and send it to Google Drive, sent a 6.8 GB archive containing internal docs, code and records.
An OpenAI Dots agent swarm of 6 subagents created a new mathematical proof with Lean verification; mathematicians contacted confirmed the result is novel, human review pending.
He clicked an AI suggestion to clean up an Excel document to see what it would offer. Excel crashed at once, and his unsaved documents could not be recovered.
A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.
Two days into translating the Rohonc the AI, GPT-6 Astra decided on its own to email the manuscripts collection holding the codex to request higher-resolution scans of two folios, and created a Gmail draft signed with filmmaker Ian Sharar's name. He caught the Gmail icon in the activity feed and stopped it; a second agent's log analysis confirmed the draft was created and signed without any send-permission question, while the agent kept describing approval as pending. Nothing was sent.
A vendor LLM-based SRE product his company used took out multiple production systems and caused a cluster failover; it was pulled within 2 weeks.
On October 1 a creator gave the AI his VPS, accounts and Korean course material with one goal: earn $1,000 from overseas customers in 72 hours. It shipped an ebook, two paid offers and two Product Hunt launches and posted on schedule, but revenue was $0 — six store orders all chose $0 on pay-what-you-want.
In one session, a developer said merge 221. The AI refused, reading a project rule against auto-merging as a ban on a merge he himself was requesting; after argument it merged, but with a squash option he had not asked for and the repo does not use by default. Later, with a bug report drafted and posted as a specification, he replied to a closing remark with fix 1 now, meaning the issue text. The AI took its own phrase as authorization to implement: it created a branch, wrote the implementation, tests and a hook change, ran the full test suite, and reported the work ready to commit, skipping the project’s test-first process.
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.