Gaby Hersham built a nightly automation in which the AI reads the roughly 20 school emails her family gets each week and adds the important dates to the family calendar, ending the manual trawl through newsletters and PDFs.
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.
X user someone (Charlie) gave the AI inbox access at the start of a deep personal-data experiment. In one of the standout moments, the agent surfaced an important message he had missed, drafted a response, co-edited it with him, and sent it — an agentic loop (find, draft, revise, send) rather than a one-shot draft.
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.
Harry McCracken's Dot, Chip, cross-checked his calendar against his email and spotted that a speaking engagement he had entered on one date had been rescheduled by the organizers to a different day, which the confirmation email showed. He says he would otherwise have shown up to an empty room.
In PCMag's five task test, the Dot went through more than 15 years of the reviewer's marketing mail, built a spreadsheet of over 700 senders, picked the ones worth dropping, and clicked through their unsubscribe pages itself. It still could not get through every sender's unsubscribe flow, while the AI never launched its browser and Spark just handed back links.
This only partly worked. Worth knowing before you try it.
In two weeks of real inbox-and-calendar work, The AI Crux had the AI book three conference rooms. Calendar work was functional but conservative: it refused anything outside 9-to-5 local without an explicit override, which the reviewer framed as a guardrail more than intelligence.
His charity food pantry needed a barcode scanner and stock checker but could not afford a paid system. He built one with AI in two days, and it now runs on a laptop in the pantry.
Someone posted an illustration styled as an iPhone call-history screen showing seven missed calls from unknown/spam numbers over three days (fictional numbers noted). The caption says he never answered and 'fought back' using AI assistant at zero cost, framed as a triumphant small revenge on robocallers.