ClawdBot is an open-source AI assistant that runs on your own machine or server.
You can control it from your phone using Telegram, WhatsApp, iMessage, Discord, etc.
You message it like a person, and it performs real computer tasks for you.
1) What ClawdBot is (simple explanation)
ClawdBot is an AI agent that:
→ runs 24/7 on your hardware
→ executes tasks on your computer
→ supports long context and session memory
→ works through messaging apps
→ can use tools like browser automation and system commands
So instead of “AI = chatbot”, this is “AI = operator”.
2) What makes ClawdBot different
From your raw content, the key differences are:
- Full computer control → It can control your computer with very few guardrails.
- Long memory system → It saves important info from your sessions so it improves over time.
- Messaging app interface → You can send commands through Telegram, WhatsApp, iMessage, Discord, etc.
Example commands you can send:
→ “Write this document.”
→ “Reply to this email.”
→ “Organize my desktop files.”
→ “Buy this on Amazon.”
→ “Check my inbox and summarize important emails.”
3) Where to run ClawdBot (choose your setup)
You have 2 main options:
Option A: Run it on your own hardware (best for control + privacy)
Good choices:
- Mac Mini
- PC (even RTX 4090 machine)
- any always-on computer
Why people use Mac Mini:
→ small, quiet, energy efficient
→ always-on device
→ integrates with macOS tools like iMessage, Calendar, Notes
Option B: Run it on a VPS (cloud server)
Example:
- AWS EC2 (free tier possible)
Why people use VPS:
→ no extra hardware needed
→ always online
→ easy remote access
Important note from raw content:
Running on VPS can be riskier for website logins because IP changes can break sessions.
4) Before you install, understand the risk
ClawdBot is powerful and risky because:
→ It can access your files
→ It can execute commands
→ It can install packages
→ It can interact with your network
→ If misconfigured, it becomes a security risk
Best practice:
✓ Run it on a dedicated machine you do not care about
✓ Use sandboxing if possible
✓ Do not give full access to personal accounts
5) Install ClawdBot (the normal flow)
The raw content mentions 2 common installation flows:
Flow A: Wizard setup (recommended)
You run the install command, then ClawdBot starts an onboarding wizard.
The wizard helps you configure:
→ Model provider
→ Messaging provider
→ Skills (optional add-ons)
Flow B: CLI install and manual setup
Same result, more manual steps.
6) Choose your Model Provider (AI brain)
During setup, you pick the LLM provider.
Examples mentioned in your raw content:
- Anthropic
- OpenAI
- Gemini
- other cheaper model providers
Then you authenticate using a token / OAuth flow.
7) Choose your Messaging Provider (how you talk to it)
This is the part that makes ClawdBot special.
Supported examples from raw content:
- Telegram
- Discord
- Slack
- iMessage
- many more
This means you can message ClawdBot from anywhere.
8) Connect Telegram (the easiest channel)
Telegram is the easiest to set up for most people.
High-level steps:
- Create a Telegram bot using BotFather
- Get the bot token
- Add Telegram provider inside ClawdBot
- Authorize your Telegram user ID
- Test by sending a message
After this, you can text your agent like:
→ “Research this company.”
→ “Summarize my last emails.”
→ “Create a file on desktop.”
9) iMessage setup (powerful but dangerous)
iMessage is the “wow factor” setup.
How pairing works (from your raw content):
- Send a message to trigger pairing
- ClawdBot generates a pairing code
- Paste pairing code into ClawdBot environment
- Once approved, you can text it from iMessage
Warning:
If you run this on your personal Mac, it may access personal iMessages.
Best practice:
✓ Create a separate Apple ID for the agent
✓ Run ClawdBot on a dedicated machine
10) ClawdBot Gateway Dashboard (what you get after setup)
After installation, ClawdBot gives you a dashboard (gateway UI) where you manage:
→ Channels (Telegram, WhatsApp, etc)
→ Instances (where it runs)
→ Sessions (chat sessions)
→ Cron jobs (scheduled tasks)
→ Skills (extensions)
→ Nodes and config
This is where ClawdBot becomes more than a chatbot.
11) First tasks to test (safe starter tasks)
Use simple, low-risk tasks first:
Task 1: Create a file
→ “Create a file on my desktop named Notes.txt”
Task 2: Organize files
→ “Rename these files 1 to 10 and move them into a folder named Thumbnails.”
Task 3: Research
→ “Research [company name] and give me a 3 bullet summary.”
These confirm:
✓ it can read directories
✓ it can write files
✓ it can execute steps correctly
12) Skills system (how ClawdBot gets smarter)
Skills are like instruction packs that teach ClawdBot how to do specific workflows.
Skills mentioned:
→ Claude Hub (skill marketplace)
→ web searching
→ email tools
→ Google services
→ other plugins
Why skills matter:
- Without skills, agent behavior is messy
- With skills, it follows consistent patterns
13) Cron jobs (scheduled automation)
This is a big feature.
Cron jobs let ClawdBot run tasks automatically on a schedule.
Examples:
→ check inbox twice a day
→ monitor something every hour
→ send you a daily summary
This is how you move from “agent” to “automation system”.
14) Security hardening (do this early)
Your raw content highlights major security concerns, so your setup should include:
SSH security (if using VPS)
Recommended changes:
→ disable root login
→ disable password login
→ use SSH keys only
Permission control
Do not give passwordless sudo unless it’s a throwaway VPS.
Secrets management
Do not send API keys and passwords in chat.
Use a secrets manager if possible.
15) What people are using ClawdBot for (real use cases)
From your raw content:
→ automated trading and monitoring markets
→ scanning job boards and auto-applying
→ customer support automation
→ managing multiple social media accounts
→ clearing inboxes and drafting replies
→ calendar management
→ file cleanup and organization
→ flight monitoring and check-in workflows
→ building apps and deploying code via GitHub workflows
16) The right way to think about ClawdBot
ClawdBot is not “another AI tool”.
It is:
→ an always-on agent
→ connected to your real systems
→ triggered from messaging apps
→ capable of running workflows without you sitting at the PC
If you set it up correctly, it becomes your remote operator.
