An independent shop owner says supplier fees creep up a little at a time and stop getting checked. He handed his statements to the AI, which pulled the numbers and drafted a renegotiation email that he read and sent himself. He ran the same pattern on a water cooler contract, where the bot found the notice window in the terms and drafted a calm email.
This only partly worked. Worth knowing before you try it.
She asked the AI to erase her digital footprint. It found data broker sites she had never heard of, wrote the removal messages, opened its own browser and filled out the opt out forms, and it checks back every week until her info is gone.
This only partly worked. Worth knowing before you try it.
A soil researcher had the AI search papers and read his draft files to turn a rejected article idea into a data driven study, and he kept replying please continue. The AI then used his connected email account to write to five researchers asking for their data, and the replies gave him a data set covering more than 50,000 sediment areas and moved the project forward.
This only partly worked. Worth knowing before you try it.
His insurer denied a cholesterol lab charge of about $300 as experimental. He used AI through the fight: the first appeal was denied as well, and the case is now at external review. He says the document work to get this far would have been out of reach on his own.
$300one time
This only partly worked. Worth knowing before you try it.
Pat Simmons gave his Dot László a shopping list to buy on Amazon, but Amazon blocked its cloud browser immediately and the Dot refused to circumvent the block. Falling back to Chrome on Simmons's own computer, it discussed choices over Slack and built a cart, but no purchase was completed.
This one went wrong. See what happened before you try it.
The AI and the AI balked at early PHP CVE investigation and at testing PoCs, slowing protection of customers; he switched to GLM 5.3 to mitigate and later used AI for the fix.
This one went wrong. See what happened before you try it.
Let the AI build and deploy a project that flickers his Lifx bulb when commits to open source projects land, though it stopped around 11 pm that night.
This only partly worked. Worth knowing before you try it.
A business user asked the AI to duplicate a template; the request bounced between chats for an entire day, each claiming the project belonged elsewhere or that it lacked access to make the change. Contradictory explanations piled up and no usable result was produced, so the business is migrating away.
This one went wrong. See what happened before you try it.
A Japanese solo operator who runs his micro-company's chores (contact checks, record-keeping, several times a day) through AI schedules found on Oct 6, 2026 that the 12:00, 15:00 and 18:00 runs had all silently not happened: schedules registered inside a conversation live only in that conversation and disappear when it closes, with no error and no notification; he noticed about 10 hours later. He built a separate watchdog: a roughly 30-line launchd shell script that checks, 20 minutes after each scheduled run, whether the day's journal file was updated, and if not, uses a headless claude -p call restricted to a single Slack-send tool to alert him with fixed wording (with a Mac notification fallback). From Oct 7 to 12 it logged 30 OK checks and one successful test alert; it has not yet caught a real stall.
This only partly worked. Worth knowing before you try it.
A user asked the AI to download a data export from five one-time links. The AI opened all five at once into the wrong app, so nothing downloaded, then opened four more in a browser without checking the first batch had failed. About ten windows and tabs later the one-time links may be used up. In the same session the AI also lost a feedback draft it had queued for him.
This one went wrong. See what happened before you try it.