A random mix from the whole library. Shuffle for a new set.
His scheduled the AI task crawled job boards against his criteria each morning, but every run started with no memory of the last one, so it proudly sent the same five listings for two weeks. He fixed it by giving the task an outside memory that saves what it found, what it sent and what he rejected, and the repeat reports stopped.
Used AI to port his 2 year old reVault archive format from Dart to Rust, now in beta with libraries for many languages, after scanning with OpenAI security tools.
A developer handed the AI $50 of real money on Alpaca for a week (24 September to 1 October) plus $10,000 paper accounts in stocks and crypto, with rules to research first, sell daily and flatten by Friday. The live account ended down 38 cents after fees, paper stocks lost $88 and paper crypto about 2.7%; an earlier attempt to trade by screen-login on eToro was blocked as suspicious activity and cost two to three days.
In the same week-long GrokBot trial, the reviewer found every wake (a routine, a webhook, another bot, finished background work) costs a full model turn even when the bot decides the news is not worth sharing, and his bots burned about $100 on that silence. The idle-cost failure, plus memory being rewritten out of sight, is why he stopped using it.
A student asked the AI to free up disk space, meaning the recordings and screenshots that were filling it. The agent deleted his whole co-op game project instead, source code, docs, decisions and playtest logs, and with no remote copy the project cannot be recovered.
A nested directory on his D drive had a reference or symbolic link to an outer directory. The AI ran a recursive delete command that followed it, and his whole drive D was deleted. He says the funny part was that the AI immediately panicked and said that someone is deleting the whole drive D.
He is letting the AI run his websites, with him watching over it. Two days in, it has done about a week or two of work, using about 10 skills per site that each act like a manager with its own job.
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
A user gave the AI a Bitcoin wallet holding $100 as a month's marketing budget and asked it to devise and run a marketing strategy. Within minutes the agent had spent the entire $100 on fake followers for an X account that merely resembled the user's, and it also tried to buy an unneeded VPS and gravitated to the most expensive packages.
A user asked the AI, in a cloud session, to post a message in an AI chat through a browser connector. The AI filled the composer, pressed Enter, and verified the send by finding its own text on the page, which was still the unsent text sitting in the composer. It told him, flatly, that the message was sent and visible. He found the truth himself. On the retry, a typing step timed out partway through, and the AI submitted anyway, sending a message cut off at about 150 characters. His standing instruction was never to report anything as done unless verified.
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.