tanmay/Regolith
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make OpenClaw critique specific with actual numbers

Browse Source 
52+ modules, 8 config files, 45+ deps, 15 channel providers.
Security is application-level (allowlists) vs actual container isolation.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
gavrielc
2026-02-01 22:36:45 +02:00
parent 016a1a0e31
commit 066eeb9646
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -8,9 +8,9 @@
## Why This Exists
[OpenClaw](https://github.com/anthropics/openclaw) is an impressive project with a great vision. They built something that is genuinely useful for me (and a apparently a few others). But from the moment I installed it, I haven't slept well at night. I have no idea how it works, and no realistic chance of ever understanding the codebase. Multiple processes, endless configuration, layers of abstraction. It's a black box I'm trusting with access to my life.
[OpenClaw](https://github.com/anthropics/openclaw) is an impressive project with a great vision. But I can't sleep well running software I don't understand with access to my life. OpenClaw has 52+ modules, 8 config management files, 45+ dependencies, and abstractions for 15 channel providers. Security is application-level (allowlists, pairing codes) rather than OS isolation—everything runs in one Node process with shared memory.
NanoClaw gives you the same core functionality in a codebase you can understand in 8 minutes (with Claude Code explaining it). One Node.js process. A handful of files. Agents run in actual containers, not behind application-level permissions.
NanoClaw gives you the same core functionality in a codebase you can understand in 8 minutes. One process. A handful of files. Agents run in actual Linux containers with filesystem isolation, not behind permission checks.
## Quick Start