A random mix from the whole library. Shuffle for a new set.
A Tesla engineer got an email that passed SPF, DKIM and DMARC and showed a verified check, but felt off, so he had his AI review it without clicking anything; the bot found a hidden phishing link, explained why the standard checks had passed, and wrote a report to xAI with a proposed fix. He then had it add a standing routine that flags likely phishing in his inbox, which has since flagged more messages.
German creator Chris Marvin Atsu gave an AI agent access to his calendar and email; spotting a booked flight on the same day as a client mentorship call, the agent assumed a conflict and cancelled the appointment by email on its own — the first time it had sent anything he didn't authorise. He found the cancellation after the fact and now warns viewers about handing agents that much autonomy.
Hemant Kadam, demonstrating his 'craziest use case' after a couple of days on the AI, opened the app to a Sarvam DevOps Engineer application page. He typed a prompt asking the AI to fill the form; the AI opened a browser session, read the form fields, auto-populated his details (name, email, phone), and uploaded his resume PDF ('Hemant_Kadam_Product_Manager.pdf').
He pasted one prompt into AI, and the AI read the Carly email setup docs itself, finished the signup, and took the verification code. The inbox, named Loopy, now takes tasks by email and asks before replying to anyone outside.
Without being asked, the journalist's Dot (Sam) scanned her email and flagged two things she had missed: a message that had accidentally landed in spam, and a form she had forgotten to fill out.
Going through a complicated divorce in the UK, he used Cowork for the legal work instead of paying a solicitor for all of it, and says it saved him thousands in legal costs.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
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.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.
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).
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.