How I AI

I gave Clawdbot (aka Moltbot) access to my computer, calendar, and emails: Here’s what happened

469 snips
Jan 28, 2026
A hands-on run with an autonomous AI agent given screen, calendar, and email access. Installation headaches, dependency chaos, and real security warnings are explored. Testing the agent as a personal assistant reveals calendar mishaps, email impersonation risks, and surprising research strengths. The episode digs into permissions, model choice, latency pains, voice messaging, and what a safe consumer agent might look like.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
ADVICE

Grant Minimal OAuth Scopes

  • Check OAuth scopes carefully: Claire noticed the agent requested full read/write/delete access when only calendar read was needed.
  • Only approve minimal scopes (read vs write) required for the task.
ANECDOTE

Assistant Workflow Instead Of Impersonation

  • Claire asked CloudBot to add a Vercel event and had it create an event on its own calendar then invite her.
  • The agent handled invites and duplicates but required back-and-forth to avoid direct impersonation.
INSIGHT

Latency Undermines Fluid Interaction

  • Expect high latency: Claire found CloudBot slow because it spawns sub-agents and batches work.
  • Latency hurts the interactive feel compared to instant chat models.
Get the Snipd Podcast app to discover more snips from this episode
Get the app