Video summary
I gave Clawdbot (now Moltbot) access to my computer, calendar, and emails: Here’s what happened
Main summary
Key takeaways
Summary of the Video: “I gave Clawdbot (now Moltbot) access to my computer, calendar, and emails: Here’s what happened”
Overview of Clawdbot / Moltbot
- Clawdbot (recently renamed Moltbot) is an open-source autonomous AI agent designed to run on local machines or cloud VMs.
- It is self-learning, capable of spinning up sub-agents using Claude Code and other agent harnesses.
- Intended to automate tasks such as managing calendars, emails, and other personal productivity workflows.
- Accessible via messaging platforms like Telegram, WhatsApp, iMessage, allowing remote interaction including voice notes.
- Does not require specialized hardware; can run on modest machines (e.g., MacBook Air) or low-cost cloud instances (e.g., $5 AWS VM).
- Claimed to be powerful but comes with significant security risks due to deep access to personal data and system files.
Installation & Setup Experience
The installation process was described as complex and time-consuming, involving:
- Manual installation of dependencies such as Node.js, Homebrew, and Xcode.
- Onboarding steps including:
- Creating API tokens and gateway tokens.
- Setting up Telegram bot integration via BotFather for secure communication.
- Configuring OAuth credentials for Google APIs (Calendar, Gmail, Docs) through Google Cloud Console.
- The setup is not user-friendly for non-technical users, requiring detailed knowledge of OAuth, API scopes, and Google Cloud Console.
- Security warnings are prominently displayed; users must be cautious about granting permissions and scope access.
Key Features & Use Cases Tested
-
Personal Assistant Tasks
- Managing calendar events, scheduling and rescheduling podcast recordings.
- Accessed a dedicated Google Workspace email with limited permissions instead of full personal account access.
- Used a dedicated vault in 1Password for storing secrets and API keys.
-
Calendar Management
- Claudebot could read calendar events and categorize them.
- Struggled with time zone conversions and date accuracy, often setting events one day late.
- Limitations in calendar API usage, such as inability to handle recurring events.
- Conflicts occurred when both user and Claudebot modified the calendar simultaneously, causing data inconsistencies.
-
Email Handling
- Claudebot could send emails but sometimes impersonated the user incorrectly, sending emails from its own account but signing as the user.
- Clear prompting and instructions are critical to avoid miscommunication and identity confusion.
-
Voice Interaction
- Supports voice notes on Telegram, both sending and receiving, enabling hands-free interaction.
- This feature was highlighted as a magical and user-friendly aspect of the tool.
-
Coding & Development
- Asked Claudebot to build a Next.js app documenting their conversation with redacted sensitive info.
- Deployment was complicated due to lack of integration with GitHub or deployment platforms.
- Coding experience was slow and not ideal compared to other tools like Devon, Cursor, or direct Claude Code usage.
- Sending screenshots and files via Telegram was noted as a useful interface feature.
-
Research & Analysis
- Tasked Claudebot to research Reddit for user needs around Chat PRD and generate a report.
- Delivered a well-structured, actionable markdown report via email.
- Considered one of the best use cases, as latency was less of an issue due to asynchronous nature of research tasks.
Product & User Experience Insights
- Claudebot is positioned as a powerful but risky AI assistant for personal productivity.
- Interaction latency is significant, making it feel slower compared to instant chatbots like ChatGPT or Claude Code.
- Security concerns are paramount due to deep access to emails, calendars, files, and secrets.
- Currently best suited for developers, hackers, or technically savvy users willing to accept security risks.
- Prompting and clear instructions are crucial to avoid unintended actions such as impersonation or data loss.
- The tool’s autonomy and self-learning capabilities are impressive but can lead to unpredictable or incorrect behavior.
- The interface of chatting with a fully autonomous AI agent via messaging apps is compelling and shows potential for the future.
Broader Industry Context & Final Thoughts
- The speaker believes big tech companies (Google, Microsoft, Meta) are best positioned to build safe, consumer-friendly autonomous AI assistants due to their control over data and infrastructure.
- However, these companies may lack the “bravery” or speed to experiment as boldly as Clawdbot’s open-source approach.
- Startups face challenges building similar tools due to data access restrictions and compliance hurdles with Google and Microsoft APIs.
- There is a tension between product usability, security, and autonomy in current AI agent tools.
- Overall, Clawdbot offers a fascinating glimpse into the future of personal AI agents but is not yet ready for mainstream use.
- The speaker plans to remove Clawdbot from their machine due to security concerns but remains interested in the concept and future developments.
Key Takeaways
- Clawdbot is an open-source, autonomous AI agent capable of performing real-world tasks but requires technical expertise to set up and manage securely.
- Offers multi-modal interaction (text, voice) and integrates with calendars, emails, and other productivity tools.
- Major limitations include slow response times, security risks, difficulty with time zone and calendar event management, and imperfect email handling.
- Best suited currently for hackers and developers with high risk tolerance.
- The vision of a personal AI assistant that can communicate naturally and act autonomously is compelling but needs safer, more polished implementations for broader adoption.
Main Speaker / Source
- Claire (ClaVo) – Product leader, AI enthusiast, and host of the “How I AI” podcast.
- Provides a hands-on review, tutorial, and analysis of Clawdbot/Moltbot from installation to real-world usage scenarios.
End of Summary