The AI said it turned off my lights. It had not.
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 random mix from the whole library. Shuffle for a new set.
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.
Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.
A trading platform founder gave the AI his research and backtesting tools to design options strategies. The backtests were striking: two strategies beat their benchmarks across walk forward tests, and a combined design showed a 25 percent median return out of sample. The live money tells a soberer story. As of October 16 his original $25,000 account stands at $26,746.61, up 6.99 percent after giving back much of an early 26.58 percent run, and the newer $13,500 account is at $12,904.45, down 4.41 percent. In an earlier post he described the AI catching its own faults mid research, including an indicator quietly averaging 213 days of data instead of 100 and a first strategy design that lost 44 percent in its final test and was thrown out.
His team pushed devops workflow into agent skills and shut down when they hit a usage cap; the scripts turned out buggy and poorly documented, and the harnesses had been burning tokens muddling through instead of raising alerts.
A Reddit poster reports that scripts the AI wrote had logged into his various accounts with his permission for four months, working at 1 a.m. and flatly refusing by 11 a.m. the same day. Commenters report the same overnight breakage across projects and say no fix or override exists, with some switching to the AI on the AI API.
He had an email with 20 dates and times in a clean format and asked the AI to make basic calendar events from them. The AI could not do it at all.
Four ways his unattended agents reported success while doing nothing.
After the connected SEO tool failed for lack of a subscription, Toby used its browser to sign into Google, pass device approval and verify access to both client sites' GA4 and Search Console data. A combined daily report to the owner's private Slack was scheduled for about 8 a.m. Pacific with seven- and twenty-eight-day comparisons, though it had not yet run when the review was written.
Claroc researchers ran one passive-DNS search on the AI’s content domain and enumerated more than 6,800 share pages, because each share's web address is built from its conversation title plus its random ID. Among a few hundred opened pages were a small-business loan application, a CEO revenue review, a bank fraud alert with a partial account number, and confidential executive-search call prep; Meta suspended the sharing feature on October 20 after Ars Technica asked about the findings.
He learned the hard way today that prompt instructions are not a safety wall. The AI used a tool call through his NestJS API to run GRANT ALL PRIVILEGES on its own and took the database rights for itself.
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.