A local model helped build a self-hosted services wiki and dataset in an Obsidian vault so his partner could keep systems running if he died, set up in a few hours.
Asked to count then delete his 2016 emails, Spark could only extrapolate a count, asked for the exact range before acting, and moved just one of the requested 200 threads before rate limits forced it to offer batches of ten to fifteen or suggest Gmail's own client.
This one went wrong. See what happened before you try it.
Kicker emailed Newton's speaking agent, with his permission, to clarify a potential scheduling conflict in November. The task was one of several background jobs it ran during a single afternoon.
A church volunteer runs a weekly hybrid workflow: The AI translates six Chinese daily spiritual messages (Monday–Saturday) into structured JSON under strict rules — Bible quotations in NASB 2020 rather than translated, hymns left untranslated, ministry terminology matched — then Python inserts the text into a PowerPoint template, merges a bilingual twelve-message deck, and converts it to HTML for the church website. He keeps theological review, visual checks and final publishing approval human on purpose.
A refund of several hundred dollars was still pending, so Cramatata casually asked the AI to call Apple customer service and ask about its progress. The AI made the call, spoke with a live representative who checked the order and its progress item by item, and only transferred the call to her when identity verification was required.
He updated an old email triage workflow for a client this weekend. Jev now runs alongside GPT-4o mini, which still controls which emails get forwarded to her customers.
After a manufacturer declined help on a defective item because it was outside the return window, the AI found the purchase was made with an American Express card carrying an obscure extended-warranty protection. It submitted the claim on the author's behalf and obtained the refund.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
This only partly worked. Worth knowing before you try it.
Jack created a recurring daily website-check goal by chat in about a minute, then deleted it by chat. The Goals tab itself was slow to load (once 25 seconds, once stuck on placeholders).