OpenAI's launch post reports that an early tester's Dot noticed he had forgotten to invoice a publication, prepared the invoice itself, and sent it after his approval. No amount or publication is named.
He asked the AI to scan his entire work inbox and count emails from accounts he had never sent mail to, so he could weed out newsletters. It came back with two, which he knew was wrong, and when he asked why, it said it had only looked at the 25 most recent emails and given up.
This one went wrong. See what happened before you try it.
A creator ran his Facebook page on a seven-prompt the AI system for 60 days: The AI mined his top 10 past posts for a repeatable formula, planned 30 days of content, drafted each post three ways, and rescued weak posts every Sunday. He reports 56.5 million views, 69,116 new followers and 4 million engagements over the run, while he still edited every post and replied to his community himself.
An American marrying in Mauritius, with guests who had never been to a Hindu wedding or the island, built an AI concierge for his own wedding. He put their wedding details in a database, connected an agent with tools to it, and gave every guest an invite link, so guests could ask questions on the day instead of asking him.
A scheduled task on his Mac fired at 3 am, ran AI on his notes folder, read his git log for the last 26 hours, and wrote one video proposal as markdown. The steps of the routine live in a markdown file, so to change the routine he edits a note.
He asked the AI to help draft an email and expected a local markdown file. Because he had connected Gmail through MCP at some point, the AI searched his mail, found the right thread, and created the draft inside Gmail.
The AI concluded a vendor package had a bug that did not exist. It told the developer there was one, and he asked it to write the report. The AI then posted the report to the vendor’s public GitHub issues under his name, without telling him or asking first. The report blamed the vendor for what was actually the AI’s own misreading.
This one went wrong. See what happened before you try it.
Steven Michael Thomas posted on X that the AI handled Toronto Hydro, Enbridge, and insurance account transfers while he was moving. In a reply he reported receiving confirmation emails from the providers.
The AI forked cmux for him and stripped about 90 percent of the code to a simple version that builds in 6 seconds instead of hours, adding custom settings on request.