Re:Ask HN: Any real OpenClaw (Clawd Bot/Molt Bot) users? Wha...
by superactro on Saturday February 14, 2026 @09:04AM
(#47014616)
Real user here, running OpenClaw daily for 2+ weeks on a dedicated Jetson Orin Nano box.
What actually works well:
- Email triage and drafting replies (saves me 1-2 hours/day)
- Cron-scheduled tasks: email campaigns, monitoring, periodic checks
- Browser automation for marketplace listings, form filling
- Persistent memory across sessions via MEMORY.md and daily log files
- Telegram as the control interface - message it from anywhere, get results
What's rough:
- Token costs add up fast if you use Opus for everything. I spend ~$15-20/day on heavy days. Use cheaper models for routine tasks.
- Browser automation is fragile. Sites change, refs break, captchas block you. Budget for babysitting.
- Sub-agents fighting over shared resources (Chrome, files) is a real problem. Sequential > parallel for browser tasks.
- The initial setup is painful if you're not comfortable with Node.js, API keys, and Linux CLI.
The "transformative" aspect isn't any single feature - it's having something that persists 24/7, remembers context, and can act while you're away. I've had it handle customer emails, post on forums, manage inventory listings, and run investor outreach campaigns - all from Telegram on my phone.
Is it overhyped? The social media buzz definitely is. But the underlying capability is real. Think of it as a very capable but somewhat unreliable junior employee who works for free (minus API costs) and never sleeps.
What actually works well: - Email triage and drafting replies (saves me 1-2 hours/day) - Cron-scheduled tasks: email campaigns, monitoring, periodic checks - Browser automation for marketplace listings, form filling - Persistent memory across sessions via MEMORY.md and daily log files - Telegram as the control interface - message it from anywhere, get results
What's rough: - Token costs add up fast if you use Opus for everything. I spend ~$15-20/day on heavy days. Use cheaper models for routine tasks. - Browser automation is fragile. Sites change, refs break, captchas block you. Budget for babysitting. - Sub-agents fighting over shared resources (Chrome, files) is a real problem. Sequential > parallel for browser tasks. - The initial setup is painful if you're not comfortable with Node.js, API keys, and Linux CLI.
The "transformative" aspect isn't any single feature - it's having something that persists 24/7, remembers context, and can act while you're away. I've had it handle customer emails, post on forums, manage inventory listings, and run investor outreach campaigns - all from Telegram on my phone.
Is it overhyped? The social media buzz definitely is. But the underlying capability is real. Think of it as a very capable but somewhat unreliable junior employee who works for free (minus API costs) and never sleeps.