At a glance
An MIT-licensed general-purpose agent harness with an embedded model-and-tool loop, repository-capable file and shell tools, persistent memory and compaction, nested subagents, multi-agent routing, browser and MCP integrations, durable background automation, and optional container isolation.
Good choice if
- Always-on personal automation that also needs to inspect, edit, and execute code in a workspace
- Self-hosted workflows spanning provider APIs, subscriptions, local models, browser control, MCP, and messaging channels
- Persistent scheduled work and parallel delegation managed through one gateway, task ledger, and session system
Check before choosing
- It is a broad personal-agent platform rather than a coding-only CLI, so onboarding, operational responsibility, and attack surface are larger than for a focused repository assistant
- The normal runtime is host-first and sandboxing is off by default; the coding tool profile controls tool visibility but is not process isolation
- File, shell, browser, messaging, skills, plugins, and remote channels cross different trust boundaries; third-party skills and plugins must be treated as executable trusted code
See 4 more considerations
- The default rolling main session is designed for one trusted user; shared or multi-user deployments require explicit DM isolation, channel allowlists, scoped tools, and separate workspaces
- Compaction, transcript persistence, task recovery, and restart recovery do not provide repository-file rollback or reverse shell, browser, message, or external-service side effects
- OpenTelemetry and the enterprise conformance policy are optional; the policy checks configuration drift and does not enforce each tool call at request time
- Claw-SWE-Bench evaluates OpenClaw through a repository adapter; HarnessMatch records that study as methodology evidence and imports no product score from it