The municipal election had a huge list of candidates and felt overwhelming. She asked the AI to study them and build a short quiz that asks voters their views, then ranks the candidates to match, with links to their platforms so people can check.
A man testing the AI as an email triage agent found it had buried an urgent warning, that his Railway and Anthropic keys had been leaked and needed rotating as soon as possible, under 50 routine deploy and admin email notifications.
This one went wrong. See what happened before you try it.
Eleanor Konik had the AI and AI team up on dashboards for local nonprofits. The AI did the early research and dug up grant chances the groups had not seen, like a group that pays for field trips to battlefields, a free textbooks program for private schools, and creative arts projects, and the lists were put behind a password for her friends to use.
Gannon Meyer (210K followers) named his AI 'Oscar' (dachshund avatar) to survive 'one of the most chaotic but manageable periods of his life.' The demo shows Oscar drafting and sending an email to a photographer about wedding timing at Perona Farms, removing sales calls from his September calendar, and tracking meals and weight-loss progress toward a wedding goal — while remembering personal context like his recent pickleball ankle injury. Oscar proposes actions but executes only after a
NYC creator John Carl Lebrilla Quilario demos his personal AI agent, named Quinn, through text messages and screen recordings. He texts Quinn to clear his messy calendar for an upcoming shoot week — Quinn cancels four calls while keeping shoots and routine blocks.
A Business Circle writer wanted to cancel a weed-overrun yard service, but the company only allowed cancellation by phone. He handed the task to the AI, which opened the company's online chat, argued with customer support through the back-and-forth, and got the cancellation completed — the user never picked up the phone.
On its first scan of the agency owner's connected Slack and calendar, the Dot Toby surfaced a Monday client discussion involving work outside the budget alongside a calendar overlap, plus another meeting conflict on Wednesday. It connected information across both apps without being fed anything manually.
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.