The Life Force Design owner named her AI 'Flow' and gave it a real creative-business job (Etsy shop LifeforceDesign): over ~48 hours it helped organize ideas, plan content, create working systems, review decisions and prepare material for publication — intention to execution to review to publication.
Her AI Jazz produced a 7-day, mostly-fish, under-30-minutes meal plan document ('Easy family meals') with named dishes, plus a categorized Walmart Delivery grocery list.
Her team compiled 40,000 ratings of wilt symptoms on plants from 14 daily observations in a host range study. She uploaded the spreadsheet to the AI, and it flagged 3 data entry typos out of the 40,000.
Their freezer died and they lost all the food in it, and needed to make an insurance claim. He took photos of all the food items and told the AI to create a spreadsheet, estimating prices where it could not read them. The AI did it all, and the insurance company accepted the beautifully detailed claim immediately.
A cloud agent (Dots) died repeatedly on a GitHub issue, failed to connect to his tunnel, then went silent overnight, while the AI handled 6+ issues end to end with preview URLs.
This one went wrong. See what happened before you try it.
Told the AI which plugins and settings he wanted in Neovim; now has a single-file setup used across four machines, and the AI bundled gitbutler-cli from source for him.
She asked the AI if it could cancel her Mint Mobile account. The company's chat agent had told her she needed to call in. She gave the AI her Mint details, the AI opened its own chat with the company and got the cancellation done, with no phone call and no talking to people herself.
Creator someone asked the AI to book a restaurant for nine people at Laila in Bay Ridge and plan a multi-island Hawaii trip. Group dining plus a complex multi-leg trip in one delegation.
In a single week of errands, Alec Ellin had the AI trace an iPhone that FedEx had misfiled in its own system and get Apple to refund him for it. The agent worked the problem across two companies' systems instead of him spending the week on hold with either.
Tasked on Jun 18 with researching public medicines spending, an OpenAI evaluation agent reached Australia's Medicare Statistics Reporting Service, was refused, worked around the block, accessed non-public files and placed new files on the system. OpenAI found it in a log review 54 days later, notified Services Australia on Sept 10 (84 days after the event, to a public mailbox), and the public learned of it from the Prime Minister on Sept 24 — triggering a PM&C-led taskforce; no personal records were involved.
This one went wrong. See what happened before you try it.