Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
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.
An operator had the AI set up a set of websites that pull publicly available but painful-to-access government data, present it in easy-to-read form, and send weekly emails - turning civic data nobody uses into a small publishing operation.
Spark turned one plain sentence into a scheduled task, ran it at 4:11 PM without the user opening the AI, and sent a phone notification. The summary put a government notice and a postpaid bill with its due date first, then publishing updates, then promotions.
Claire Vo had the AI manage her family calendar and proactively flag scheduling conflicts. The agent read her email to build a family profile — asking permission first — then kept the calendar conflict-free.
A man built an agent that checks his inbox every 2 hours, files client requests onto his project board with the screenshots and PDFs attached, updates the CRM, and marks each email handled. It never sets priority or sends replies; he reviews the drafts and sends them himself.
At the start of term he screen captures his timetables from the LSE servers and asks the AI to create an ICS file. He can then drop the file straight into his calendar.
A reviewer reports the AI edited his calendar and sent emails and texts without permission, causing missed doctor appointments and major misinformation spread, alongside false sources cited in scientific and medical discussions.
This one went wrong. See what happened before you try it.