Problem
Development workflows are tethered to a laptop. When you're commuting, walking, or otherwise away from a keyboard, you lose access to your entire development environment. You can read code on your phone, but you cannot build tools, run them, iterate on output, or push to Git. Quick fixes and small feature work pile up until you're back at a desk.
Solution
Use Clawd Bot on WhatsApp as a conversational interface to a full development environment. The bot has file system access, CLI tools, and Git -- letting you build, test, and deploy from your phone.
Setup
Register at clawd.bot and connect your WhatsApp account. The bot runs on a server with access to your configured tools and file systems.
Core capabilities
The bot exposes CLI tools through natural language:
You: Build me a CLI tool that exports Granola meeting notes to markdown
Bot: I'll create that. Setting up the project structure...
Created granola-cli/src/index.ts with commands:
- export: fetches notes from Granola API, converts to markdown
- list: shows recent meetings
Running tests now...
You: Run it against my last 3 meetings
Bot: Exported 3 notes to ./output/:
- 2026-02-08-standup.md (1.2KB)
- 2026-02-07-planning.md (3.4KB)
- 2026-02-06-retro.md (2.1KB)
All look good. Want me to push to Git?
You: Yes, push it
Bot: Pushed to github.com/yourname/granola-cli on main. Done.
Available integrations
Configure the bot with access to the tools you need:
- Git CLI: clone, commit, push, create branches and PRs
- File system: read, write, and navigate project directories
- Twitter CLI: post updates, read mentions
- Email CLI: send, read, and flag emails
- Obsidian vault: read and write notes, search knowledge base
Skills system for extensibility
Define reusable skills that the bot can invoke:
{
"name": "deploy-preview",
"description": "Deploy current branch to preview environment",
"steps": [
"git push origin HEAD",
"vercel deploy --prebuilt",
"return deployment URL"
]
}
Proactive automation
The bot can run cron jobs independently:
- Heartbeat checks on production services every 15 minutes
- Daily summary of Git activity across your repos
- Flag urgent emails and surface them in WhatsApp
- Morning briefing with calendar, PRs needing review, and CI status
Tips for production use
- Use a dedicated WhatsApp Business account rather than your personal number -- the UX is better and avoids mixing personal chats with development
- Lock down which channels and repos the bot can access to prevent accidental operations
- Context switch between projects mid-conversation -- the bot maintains context per project
Why It Works
WhatsApp is already on your phone with push notifications, reliable delivery, and a fast text input experience. By connecting it to a server-side agent with CLI access, you get the same capabilities as a terminal session but through a conversational interface. The bot translates natural language into shell commands, runs them, and reports results back. Because it has persistent access to your file system and Git credentials, the full build-test-deploy cycle works without a laptop.
Context
- A real CLI tool (granola-cli) was built and deployed to GitHub entirely from WhatsApp messages
- The memory system stores daily summaries so the bot remembers project context across sessions
- Works best for small-to-medium tasks: bug fixes, CLI tools, config changes, deployments
- Not a replacement for IDE-heavy work like complex refactors or UI development
- Security is critical: restrict file system access, use read-only Git tokens where possible, and audit the bot's action log regularly