Project review
The open agent that lives in your group chats.
A serious personal-agent harness when you want local control more than vendor polish.
By ClawBlog Reviews Desk · Drafted with ClawBlog's research pipeline; edited and accountable to the named reviewer.
82
/100
ClawScore
Strong
82
/100
Users' Score
example avg 8.2/10
Accepted, attributed sources
Github
Oct 27, 2026
Release notes document critical security updates, reliability and performance fixes applied across 78 fixes from 77 PRs with systematic maintenance audit coverage.
Reliability
Positive (+1)
Github
Oct 18, 2026
Update robustness improvements (auto-recovery, cross-device completion, stale lease handling) demonstrate enhanced system reliability.
Reliability
Positive (+1)
Github
Sep 30, 2026
Product release notes document deprecation timelines and migration guidance for plugin compatibility, supporting developer transition.
Docs & Support
Positive (+1)
Github
Sep 18, 2026
Extended Stable release with 126 merged PRs demonstrates active development and release cadence.
Momentum
Positive (+1)
Simonwillison
Aug 10, 2026
Independent reviewer identified critical authorization bypass vulnerability allowing unauthorized cancellation of other users' reservations with functional proof-of-concept.
Safety & Control
Negative (-1)
Review consensus
ClawBlog critics
A serious personal-agent harness when you want local control more than vendor polish.
82
/100
ClawScore
Strong
Review by ClawBlog Reviews Desk
Score profile
Readers
Approved reader ratings unlock at 5 ratings and stay moderated before publication.
82
/100
Users' Score
example avg 8.2/10 from 5
OpenClaw: I kept this in the loop for a month of normal feature work. The strongest part was how quickly it recovered from messy repo state without making the review process feel brittle.
OpenClaw: The setup path was smoother than expected and the defaults were sensible. I still had to tighten a few permissions for our workflow, but the day-to-day experience held up.
Example member reviews
Reader ratings for OpenClaw, sorted newest first by default.
Featured
Mara Chen
9/10 · 18 helpful
OpenClaw: I kept this in the loop for a month of normal feature work. The strongest part was how quickly it recovered from messy repo state without making the review process feel brittle.
Newest
Samira Okafor
8/10 · 8 helpful
OpenClaw: The review queue and audit trail mattered more than raw speed for us. It was easy to understand what happened, what changed, and when a human needed to step in.
Jun 14, 20268 review karma
OpenClaw: The review queue and audit trail mattered more than raw speed for us. It was easy to understand what happened, what changed, and when a human needed to step in.
8
/10
8
Helpful
Strong
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 13, 20269 review karma
OpenClaw: I liked the basic shape, especially once I stopped treating it like a magic button and gave it bounded jobs. The rough edges were mostly around longer-running context.
7
/10
9
Helpful
Mixed
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 12, 202612 review karma
OpenClaw: For repeatable agent tasks, the value showed up in the small things: clearer status, fewer surprise handoffs, and a useful paper trail when the output needed review.
9
/10
12
Helpful
Rave
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 11, 202614 review karma
OpenClaw: The setup path was smoother than expected and the defaults were sensible. I still had to tighten a few permissions for our workflow, but the day-to-day experience held up.
8
/10
14
Helpful
Strong
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
Jun 10, 202618 review karma
OpenClaw: I kept this in the loop for a month of normal feature work. The strongest part was how quickly it recovered from messy repo state without making the review process feel brittle.
9
/10
18
Helpful
Rave
Signal
Example reviews preview the voting surface, but they are not persisted and cannot receive votes.
The Criteria section is the detailed rubric behind the official ClawScore: each row carries its weight, rationale, and receipts.
Capability
Weight 1.6
OpenClaw is rated on capability from currently bound launch evidence. Unsupported details remain Analysis until receipts are attached.
Reliability
Weight 1.3
OpenClaw is rated on reliability from currently bound launch evidence. Unsupported details remain Analysis until receipts are attached.
Latest receipt: Positive (+1) · Github · Oct 27
Setup & DX
Weight 1.1
Setup remains the main drag: powerful local harnesses make the operator carry more configuration burden.
Safety & Control
Weight 1.4
The harness is strongest where it exposes the control plane instead of hiding it behind a generic chat surface.
Latest receipt: Negative (-1) · Simonwillison · Aug 10
Cost Efficiency
Weight 1
OpenClaw is rated on cost efficiency from currently bound launch evidence. Unsupported details remain Analysis until receipts are attached.
Docs & Support
Weight 1
OpenClaw is rated on docs & support from currently bound launch evidence. Unsupported details remain Analysis until receipts are attached.
Latest receipt: Positive (+1) · Github · Sep 30
Momentum
Weight 1.2
OpenClaw is rated on momentum from currently bound launch evidence. Unsupported details remain Analysis until receipts are attached.
Latest receipt: Positive (+1) · Github · Sep 18
OpenClaw is the personal-agent harness in this launch set that most clearly optimizes for operator control. The upside is obvious: local-first workflows, explicit skill and loadout concepts, and a culture that treats the agent as a system you configure rather than a feature you rent. That posture is why OpenClaw belongs near the top of the launch catalog. It gives technical operators a place to reason about permissions, tools, memory, and workflow composition without pretending those concerns disappear behind a chat box.
That control is also the tax. OpenClaw asks more from the operator than a managed coding assistant. Teams need to understand the sandbox, the skill boundary, the model/provider choices, and the operational failure modes. For a technical user, that is a feature. For someone expecting a hosted product, it can feel like a pile of sharp but useful parts. The review therefore should not describe OpenClaw as the easiest agent path. It is closer to the most operator-shaped path: more flexible, more inspectable, and less forgiving of casual setup.
The draft score rewards OpenClaw for capability, safety posture, and ClawBlog's existing coverage depth. Safety & Control is high because the project appears to make the control plane visible. Cost Efficiency is also strong in principle because self-managed operation can let a team choose providers and deployment shape. Those benefits still depend on discipline. A loose skill registry, broad shell access, or unclear approval policy can erase the advantage quickly.
The parts still needing operator review are long-run reliability, ecosystem maintenance, and whether setup complexity has improved enough for less obsessive users. ClawLab should test first-run installation, a realistic multi-step task, interruption recovery, and permission boundaries under a deliberately awkward workload. Until that happens, this is a confident draft but not a blank check. OpenClaw looks like serious infrastructure for people who want to own the agent layer. It is less compelling for teams that mostly want a vendor to own the risk.
Audience rating
Share one clear score and a short note. Approved reviews feed the Users' Score after moderation.
Checking session...
