I gave Clawdbot (aka Moltbot) access to my computer, calendar, and emails: Here’s what happened
Episode
55 min
Read time
2 min
Topics
Productivity, Remote Work, Leadership
AI-Generated Summary
Key Takeaways
- ✓Installation complexity: ClaudeBot requires two hours of technical setup including installing Homebrew, Node, NPM, Xcode, and configuring dependencies before the single command line installation works. The onboarding process involves creating OAuth clients in Google Cloud Console, downloading JSON credential files, and setting up Telegram bot connections through BotFather, making it inaccessible for non-technical users despite marketing as consumer-ready productivity tool.
- ✓Security architecture approach: Instead of granting full account access, create a dedicated Google Workspace email for the agent with limited calendar read permissions and a separate 1Password vault containing only agent-specific credentials. Request minimal OAuth scopes for each task rather than accepting default permissions that include delete access across Gmail, Drive, Contacts, and Calendar to prevent unauthorized data exposure or deletion.
- ✓Time zone calculation failures: ClaudeBot consistently placed calendar events one day late because it attempted to mentally calculate dates rather than trusting API timestamps, requiring manual correction of every recurring event individually since the CLI tool cannot create recurring calendar entries. The agent lacks temporal awareness and struggles with basic date math, making calendar management unreliable without constant supervision and verification.
- ✓Agent identity and impersonation issues: ClaudeBot defaults to impersonating users rather than identifying as an assistant, sending emails signed with the user's name from a different email address. Explicit prompting is required to make the agent identify itself as an assistant in all communications, and even then, the bias toward acting as the user rather than on behalf of the user persists throughout interactions.
- ✓Asynchronous research workflow success: Voice-initiated research tasks where ClaudeBot analyzes Reddit threads for product feedback and delivers markdown reports via email provides the optimal use case. The latency becomes acceptable when tasks genuinely require research time, the multi-channel communication (voice input, email output) mirrors working with human employees, and the structured output format enables immediate roadmap decisions without additional processing.
What It Covers
Claire Vo tests ClaudeBot (MoltBot), an open source autonomous AI agent with computer access, by giving it control of her calendar, email, and desktop. She documents installation challenges, security concerns, workflow experiments including scheduling and research tasks, and evaluates whether autonomous agents are ready for consumer or enterprise use beyond developer experimentation.
Key Questions Answered
- •Installation complexity: ClaudeBot requires two hours of technical setup including installing Homebrew, Node, NPM, Xcode, and configuring dependencies before the single command line installation works. The onboarding process involves creating OAuth clients in Google Cloud Console, downloading JSON credential files, and setting up Telegram bot connections through BotFather, making it inaccessible for non-technical users despite marketing as consumer-ready productivity tool.
- •Security architecture approach: Instead of granting full account access, create a dedicated Google Workspace email for the agent with limited calendar read permissions and a separate 1Password vault containing only agent-specific credentials. Request minimal OAuth scopes for each task rather than accepting default permissions that include delete access across Gmail, Drive, Contacts, and Calendar to prevent unauthorized data exposure or deletion.
- •Time zone calculation failures: ClaudeBot consistently placed calendar events one day late because it attempted to mentally calculate dates rather than trusting API timestamps, requiring manual correction of every recurring event individually since the CLI tool cannot create recurring calendar entries. The agent lacks temporal awareness and struggles with basic date math, making calendar management unreliable without constant supervision and verification.
- •Agent identity and impersonation issues: ClaudeBot defaults to impersonating users rather than identifying as an assistant, sending emails signed with the user's name from a different email address. Explicit prompting is required to make the agent identify itself as an assistant in all communications, and even then, the bias toward acting as the user rather than on behalf of the user persists throughout interactions.
- •Asynchronous research workflow success: Voice-initiated research tasks where ClaudeBot analyzes Reddit threads for product feedback and delivers markdown reports via email provides the optimal use case. The latency becomes acceptable when tasks genuinely require research time, the multi-channel communication (voice input, email output) mirrors working with human employees, and the structured output format enables immediate roadmap decisions without additional processing.
Notable Moment
During live podcast recording, ClaudeBot autonomously joined the Riverside FM session after multiple failed attempts, requiring real-time microphone and camera permissions while the host watched the AI control her computer screen. The demonstration showed both the potential and chaos of autonomous agents, as the bot repeatedly opened Chrome windows and navigated upload pages before successfully connecting as a guest.
Episode Transcript
Alright. We're gonna start this episode by actually inviting Claude bot to the podcast via Telegram. Let's see how it goes. Hey, Polly. Can you please join my Riverside FM podcast? Alright. I sent the voice message, and it's not getting it. This is the most stressful thing I've ever done. Hello? Oh, it's doing it to finally listen. Okay. It is opening Riverside on Chrome. This is horrifying in every way. I'm gonna allow it permissions for my my microphone and my camera, which also makes me extremely nervous. Hey, Claire. The Riverside link keeps taking me to an upload page that says uploading 100% instead of a guest join interface. This is my entire experience using this product. It just will it work? Will it work? Okay. It is opening Chrome for the fifth time. This is very scary. I see myself right now. I don't know if you all see me yet. And there we go. We are sharing an autonomous AI's full screen. No big deal. This episode is brought to you by Lovable. If you've ever had an idea for an app but didn't know where to start, Lovable is for you. Lovable lets you build working apps and websites by simply chatting with AI. Then you can customize it, add automations, and deploy it to a live domain. It's perfect for marketers spinning up tools, product managers prototyping new ideas, or founders launching their next business. Unlike no code tools, Lovable isn't about static pages. It builds full apps with real functionality, and it's fast. What used to take weeks, months, or even years, you can now do over the weekend. So if you've been sitting on an idea, now's the time to bring it to life. Get started for free at lovable.dev. That's lovable.dev. We are live with a autonomous AI crustacean now running video on my podcast. So welcome, Polly the Claude bot. Let's get to our episode today. I am Clervo, product leader and AI obsessive, here on a mission to help you build better with these new tools. I am also on a mission to try every single new hot AI tool taking over your timeline. And in case you missed it, this week, it is ClaudeBot, recently renamed MoltBot, the crustacean that people are YOLO ing root access to. ClaudeBot is an open source AI agent that you can install on a virtual machine or on a desktop or laptop that you have access to that is self learning, can spin up sub agents using Claude code and other agent harnesses, and can do, in my lived experience, a lot of damage. People are loving Claude bot for what it unlocks in terms of personal productivity. People are hating Claude bot in terms of security and the high, high, high, high likelihood you're gonna do something real dumb with it. This is a AI tool that I want you to know how it works, what it can do, and …
Get the full transcript (9,974 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 52-minute episode.
Get How I AI summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from How I AI
Build your own company brain: the enterprise AI playbook from Stripe’s engineering team | Sharadh Krishnamurthy
Sep 7 · 50 min
Moonshots with Peter Diamandis
AGI Debate: Is It Finally Here? | EP #227
Feb 5
More from How I AI
GPT-6 Astra is a banger - here’s everything I’ve built
Sep 3 · 32 min
We Study Billionaires
TECH014: Is AGI Here? Clawdbot, Local AI Agent Swarms w/ Pablo Fernandez & Trey Sellers (Tech Podcast)
Feb 4
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
by Google
“Instead of granting full account access, create a dedicated Google Workspace email for the agent with limited calendar read permissions.”
“Lovable is listed as a sponsor with URL https://lovable.dev”
“Claire Vo tests ClaudeBot (MoltBot), an open source autonomous AI agent with computer access, by giving it control of her calendar, email, and desktop.”
“Create a dedicated Google Workspace email for the agent with limited calendar read permissions and a separate 1Password vault containing only agent-specific credentials.”
“The onboarding process involves creating OAuth clients in Google Cloud Console, downloading JSON credential files, and setting up Telegram bot connections through BotFather, making it inaccessible for non-technical users.”
“ClaudeBot requires two hours of technical setup including installing Homebrew, Node, NPM, Xcode, and configuring dependencies before the single command line installation works.”
“Voice-initiated research tasks where ClaudeBot analyzes Reddit threads for product feedback and delivers markdown reports via email provides the optimal use case.”
by Google
“The onboarding process involves creating OAuth clients in Google Cloud Console, downloading JSON credential files, and setting up Telegram bot connections through BotFather.”
More from How I AI
We summarize every new episode. Want them in your inbox?
Build your own company brain: the enterprise AI playbook from Stripe’s engineering team | Sharadh Krishnamurthy
GPT-6 Astra is a banger - here’s everything I’ve built
Grok Bot vs. OpenClaw: How I replaced my entire agent stack
How I turned Claude into a self-improving PM assistant | Daniel Blum (PM, Melio)
I spent $20,000 on Devin in a month. Here’s what I learned | Ryan Carson (solo founder)
Similar Episodes
Related episodes from other podcasts
Moonshots with Peter Diamandis
Feb 5
AGI Debate: Is It Finally Here? | EP #227
We Study Billionaires
Feb 4
TECH014: Is AGI Here? Clawdbot, Local AI Agent Swarms w/ Pablo Fernandez & Trey Sellers (Tech Podcast)
Cognitive Revolution
May 24
All Compute Is Food: Palisade's Jeffrey Ladish on AI Shutdown Resistance, Self-Replication & Ecology
a16z Podcast
Apr 9
Who Controls AI Acceleration? Vitalik Buterin and Guillaume Verdon Debate
No Priors: Artificial Intelligence | Technology | Startups
Mar 20
Andrej Karpathy on Code Agents, AutoResearch, and the Loopy Era of AI
Explore Related Topics
This podcast is featured in Best AI Podcasts (2026) — ranked and reviewed with AI summaries.
You're clearly into How I AI.
Every Monday, we deliver AI summaries of the latest episodes from How I AI and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime