feat: initial companion repo for OpenClaw vs Claude Code article
40 files demonstrating every major OpenClaw capability using Claude Code: - 3 agents (researcher, writer, reviewer) - 3 skills (daily-briefing, slack-message, web-research) - 2 security hooks (pre-tool-use blocker, post-tool-use logger) - 10 self-contained examples with copy-paste prompts - Complete feature map (20 capabilities, 11 full match, 7 different, 2 gap) - Security docs including NemoClaw comparison - Automation, messaging, browser, memory documentation Zero dependencies. Clone and run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
commit
2491f5c732
40 changed files with 2037 additions and 0 deletions
15
security/README.md
Normal file
15
security/README.md
Normal file
|
|
@ -0,0 +1,15 @@
|
|||
# Security
|
||||
|
||||
Security in Claude Code is layered: permission modes set the
|
||||
baseline, hooks enforce custom rules, and settings.json defines
|
||||
tool restrictions. This is architecturally different from OpenClaw's
|
||||
container-based isolation but achieves the same goal: controlled
|
||||
agent behavior.
|
||||
|
||||
## Documents in this directory
|
||||
|
||||
| File | What it covers |
|
||||
|------|---------------|
|
||||
| `permission-modes-explained.md` | The three permission modes and when to use each |
|
||||
| `hook-based-guardrails.md` | Building custom security with PreToolUse hooks |
|
||||
| `nemoclaw-comparison.md` | Honest comparison with NemoClaw's enterprise security |
|
||||
Loading…
Add table
Add a link
Reference in a new issue