TechMitra founder Ayush Singhal asked the AI to triage his Gmail thread by thread. It proposed archiving ten promotional emails, correctly found nothing to do on other categories, and unprompted flagged a spam comment on his second website. After his approval it archived nine FYI threads and left two genuine action items.
The same Cowork setup checks his father's email for work orders and schedules his father's meetings automatically. He turned off data sharing with AI for this, so the mail is not saved anywhere else.
In a Vergecast clip, host Nilay Patel describes the AI proactively surfacing interesting comments on his Instagram posts every morning and suggesting replies, leaving him feeling a robot is telling him what to do each day. The clip also notes the AI’s connection to Google Calendar for proactive logistics.
He is treasurer for a nonprofit food co-op. He gave the AI the co-op's financial statements, some notes on what he wanted to explain, and the logos, and 20 minutes later he had a ten slide deck and separate printouts for the annual meeting.
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.
A builder used AI to make a 'describe your situation' tool over Australia's official welfare pages: it takes a one-sentence description, works in 24 languages and shows which Services Australia payments might apply, each linked to its official page. Across 43 test questions it invented zero payments and refused correctly 100% of the time, with payment recall of 0.76.
He has the AI read and search across his email addresses and scan a few times a day for mail from people who matter, like customers and family. He has basically stopped checking email forty times a day. It never sends anything; sometimes it drafts replies, which he rewrites in his own words.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
This one went wrong. See what happened before you try it.