Reviewers see BetterClaw as a practical, low-friction way to run AI agents without the usual Docker, hosting, or security setup. They repeatedly praise the fast no-code onboarding, useful visual builder, native Slack and Telegram workflows, and BYOK model, which they say keeps costs and data control clearer. Several also mention guardrails like approvals, verified skills, trust controls, and a kill switch. The main asks are better docs around permissions, pricing and custom skills, plus more templates, integrations, logging, analytics, and a more consistent UI.
@andrew_esparon different layer, same ecosystem. Hermes is the agent runtime, it's what actually executes tasks and talks to models. BetterClaw sits on top and handles the parts that make Hermes painful to run yourself: no Docker or config files, OAuth to 95+ tools with one click, credential encryption, and the trust-level permission system.
Think of it as: Hermes is the engine, we're the car. If you're comfortable in a terminal you might not need us. If you want an agent running today without becoming its sysadmin, that's the gap we fill.
Laiba here, also on the BetterClaw team.
One thing worth calling out: every agent starts as an Intern that asks before it touches anything. You promote it to Specialist, then Lead, once it stops surprising you. That's the difference between a cool demo and something you leave running while you sleep.
We built it that way because we didn't trust our own agents at first either.
Fastest first agent is a morning briefing on Gmail or Slack. Takes about a minute.
What would you want an agent to take off your plate? I'm in the comments all day.
@worksforme +1 to this. I’ve seen this firsthand on the team, and the “Intern → Specialist → Lead” progression really captures how we think about trust and autonomy. The goal isn’t just to make agents capable, but to make them reliable enough that you can actually hand things off and get back to your day. Excited to see where we take this next! 🚀
How do you decide when an agent has done enough to move from Intern to Specialist without giving it too much access too early?
Congrats @better_shaya & team!
@hamza_afzal_butt Whenever you have that confidence on your agent, people generally wait for a week, approve and then once they are sure they upgrade it to specialist and let it perform tasks without manual intervention.
I would still recommend reviewing the sensitive tasks.
Social Media, marketing, etc can be relied upon
@hamza_afzal_butt Skills are toggled individually and credentials are scoped per agent, so an agent never gets more access than it's earned — and its activity log shows the track record behind each step.
@better_shaya @hamza_afzal_butt Thanks Hamza 🙌 It's your call rather than the agent's, so you keep it at Intern until you've watched enough approvals go through clean and feel good about handing over more. Most people move one task type at a time instead of promoting the whole agent at once.
Someone on our team shared this and I set up an agent that pulls my calendar and Slack messages in the morning and sends me a briefing at 8am. That's it. That's my whole use case. Took about 2 mins
The Intern thing is smart. I would not have connected my work Gmail to something that could just do whatever it wanted. Knowing it has to ask me first made me actually try it instead of closing the tab.
@ajay_negi6 Thanks a lot Ajay!! We are so glad that you are liking the product!! :)
How does the agent 'earn' promotion, is that manual on your end or does it track some kind of track record automatically?
@abod_rehman We have kept it strictly manual - only promotes once it has earned trust from you
Not needing Docker or a VPS removes a pretty big barrier for people who just want an agent running. Congrats!
@henry_habib Exactly! That was a big part of the goal-making it easy to get started without having to deal with infrastructure first. Appreciate you giving it a try! 🙌
@henry_habib Thanks Henry! That barrier was the whole reason we built this. I watched so many people in the OpenClaw community get genuinely excited about agents, then lose a weekend to Docker networking and never come back. The AI part was never what stopped them.
The Intern that asks before acting is the part I would build the whole product around, and it is also the part that quietly decays. We run approval-gated sending on our side, and the failure mode is never the agent doing something reckless. It is the human. Reviewing every action works until the volume goes up, then you start skimming, and the ones that get through are never the obvious ones.
So the thing I would watch is what keeps an approval meaningful on day ninety. An agent that asks rarely, and only where it is genuinely unsure, is worth more than one that asks every time and trains you to click yes.
@jernej_jan_kocica This is one of the sharpest critiques of the model we've gotten, because it's true and it's not something a permission gate on its own fixes.
"Trains you to click yes" is exactly the failure mode we worry about too. Right now our answer is incomplete: Intern asks on everything by default, which is safe on day one and genuinely annoying by day ninety if the agent hasn't earned the right to ask less. We haven't built the part where it learns to only interrupt you when it's actually unsure, rather than on a fixed rule.
What we do have is the activity log as a check against rubber-stamping. If you're approving without reading, at least there's a record to catch it after the fact, which isn't the same as preventing it.
The honest version of what we should build next, based on what you're describing: confidence-based asking rather than category-based asking. Ask often early, ask rarely once it's shown it gets the boring 95% right, and always ask on the specific category you've marked as high stakes regardless of streak. That's meaningfully harder to build than "ask before every action" and probably why most of the industry hasn't done it either.
Appreciate you naming the actual failure mode instead of the reassuring one.