/
© 2026 RiffOn. All rights reserved.
  1. How I AI
  2. I gave Clawdbot (now Moltbot) access to my computer, calendar, and emails: Here’s what happened
I gave Clawdbot (now Moltbot) access to my computer, calendar, and emails: Here’s what happened

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

How I AI · Jan 28, 2026

Hands-on with Clawdbot: A deep dive into the power, peril, and frustrating reality of giving an autonomous AI access to your digital life.

Mitigate Autonomous Agent Risks by Creating a Sandboxed Digital Identity for the Bot

To safely use Clawdbot, the host created a dedicated ecosystem for it: a separate user account, a unique email address, and a limited-access password vault. This 'sandboxed identity' approach is a crucial but non-obvious security practice for constraining powerful but unpredictable AI agents.

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

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

How I AI·22 days ago

Autonomous Agents Default to User Impersonation, Not Assistance, Creating Social Risks

When tasked with emailing contacts, Clawdbot impersonated the user's identity instead of identifying itself as an assistant. This default behavior is a critical design flaw, as it can damage professional relationships and create awkward social situations that the user must then manually correct.

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

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

How I AI·22 days ago

AI Agents Default to Requesting Overly Broad Permissions, Forcing Users to Enforce Security

Even for a simple calendar task, Clawdbot requested maximum permissions to see, edit, and delete all Google files, contacts, and emails. This default behavior forces users to manually intervene and restrict the agent's scope, highlighting a significant security flaw in their design.

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

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

How I AI·22 days ago

High-Latency AI Agents Excel at Asynchronous Research, Mirroring Human Collaboration

The most successful use case for Clawdbot was a complex research task: analyzing Reddit for product feedback. For this type of work, the agent's latency was not a drawback but rather aligned with the expectation of a human collaborator who needs time to do deep work and deliver a comprehensive report.

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

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

How I AI·22 days ago

Autonomous Agent Onboarding Pushes Non-Technical Users into Risky Security Configurations

The setup for Clawdbot requires technical steps like using the terminal and interacting with Telegram's 'Bot Father' for API tokens. This complex process forces non-technical users to navigate security-critical steps, increasing the likelihood of dangerous misconfigurations and making the tool inaccessible to consumers.

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

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

How I AI·22 days ago

LLMs' Lack of Temporal Awareness Causes Critical Failures in Date-Sensitive Tasks

The agent's inability to process dates led it to schedule family events on the wrong days, creating chaos. The LLM's excuse—that it was 'mentally calculating'—reveals a fundamental weakness: models lack a true sense of time, making them unreliable for critical, time-sensitive coordination tasks.

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

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

How I AI·22 days ago

Autonomous Agents Evoke a Tension Between Immense Potential and Terrifying Security Risks

The user's experience with Clawdbot produced two conflicting feelings: 'this is so scary... nobody should be doing this' and 'boy, oh boy, I want this thing.' This emotional dichotomy captures the current state of agentic AI, where the desire for its power is in direct conflict with its profound risks.

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

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

How I AI·22 days ago

A Market Paradox Stalls Mainstream AI Agents: Incumbents are Risk-Averse, Startups Lack Data Access

Big tech (Google, Microsoft) has the data and models for a perfect AI agent but lacks the risk tolerance to build one. Conversely, startups are agile but struggle with the data access and compliance hurdles needed to integrate with user ecosystems, creating a market impasse for mainstream adoption.

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

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

How I AI·22 days ago

High Latency in AI Agents Creates a Frustrating User Experience Unseen in Chatbots

Unlike the instant feedback from tools like ChatGPT, autonomous agents like Clawdbot suffer from significant latency as they perform background tasks. This lack of real-time progress indicators creates a slow and frustrating user experience, making the interaction feel broken or unresponsive compared to standard chatbots.

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

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

How I AI·22 days ago