This directory contains a breakdown of the Clawdbot framework, generated by Gemini agents for a beginner audience.
-
- A plain English explanation of the project.
- Why it matters and who it is for.
- The "Lobster" analogy.
-
How It Works (Technical Overview)
- The Architecture: Gateway, Channels, Agents.
- Data flow diagrams.
- Key concepts: Sandboxing and Plugins.
-
- Scenario A: Standalone Mac Mini (Home Assistant).
- Scenario B: Isolated VPS (Secure Cloud Bot).
- Step-by-step instructions for both.
-
- Data locality and ownership.
- The "Pairing" system for access control.
- Docker sandboxing for safe code execution.
-
clawdbot.jsonstructure.- Critical security settings.
- Environment variable overrides.
-
- Analysis of 512 security findings by Argus Security.
- Key risks: Plaintext token storage, webhook signature bypass, and race conditions.
- Link to full remediation plan and active discussion.
-
Independent Security Audit (Saad Khalid)
- Critical RCE: "Logic Bomb" allows agents to rewrite Docker startup commands via
config.patch. - Auth Bypass: Agents can self-approve dangerous commands (missing role check in
exec.approval.resolve). - Data Risks: Arbitrary file overwrite (
nodes:screen_record) and arbitrary read (logs.tail). - Protocol Flaws: Token manipulation via pipe injection and environment variable hijacking (
LD_PRELOAD). - Note: The reported DNS Rebinding (SSRF) appears mitigated in the current version via pinned dispatchers.
- Critical RCE: "Logic Bomb" allows agents to rewrite Docker startup commands via