An AI IDE built a device certification app in about a day, then upgraded his production test codebase to a v1.0-ready state with automated configs, error handling and simulators over two weeks.
A renter hit with an Enterprise damage claim had the AI dissect the claim and draft a dispute email built entirely on its evidence gaps - photos with no timestamps and no walkthrough record showing damage. Enterprise replied the next day saying the claim was closed.
A developer threw a significant codebase at the AI. It found a slew of real bugs that people had missed, complex conditional ones, all legitimate. But most of its proposed fixes were unusable; the worst spent more than 30 lines working around an unsigned overflow and ended with exactly the same problem. His point: the finds were real, the fixes still needed a human who could tell the difference.
This only partly worked. Worth knowing before you try it.
By voice, Simmons asked László for an October 15–18 Montreal trip: a central, inexpensive Airbnb, the cheapest direct flight with an aisle seat, and a plan of things to do. The Dot compared stays, caught repeated complaints about a squeaky Murphy bed at a 4.75-star listing, filled in his flight details from his travel records, rerouted the Mont Royal walk because the cross was under construction, and stopped at checkout for him to pay.
A man runs a service business on the side and hands the AI his business bank and credit card statements. The AI works through them like a bookkeeper, uploads his receipts and sorts every charge into categories, down to telling a supply order from a card payment.
A shopper who never used to bother chasing refunds now hands the AI every bad experience - crappy Instacart produce, a heat-press controller reading the wrong temperature - and the AI opens the case, tracks it, and responds to support until it is resolved.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
This only partly worked. Worth knowing before you try it.
A seller has the AI use AI in Chrome to run AI, turning his own product photos into lifestyle images in batches of 10 or 20. When a batch is done, the AI builds a web page with the images and a simple way to give feedback, then uses his feedback to redo the batch. He uses this route to avoid paying for API use.
For years he kept a Photoshop contract just to read and write DDS texture files for his ETS2 and ATS mods. He asked the AI, and now he can convert DDS to PSD and back in batches.