Peter Steinberger: What Happens When 4.7 Million People Let It Cook

Steinberger walks through the full arc of OpenClaw — from a personal WhatsApp relay to 4.7M weekly downloads — and is unusually candid about what broke: security reports that ate months, 9,500 configuration permutations that killed velocity, and a provider pulling subscriptions with 24 hours' notice. This is a field report on the real failure modes of viral developer tools, not a victory lap. Anyone building on top of a single model provider should hear the dependency-risk section.

• Your dependencies' business model is your business model — over-optimizing for one provider (Claude) became an existential risk when subscriptions were pulled with 24 hours' notice
• Configuration explosion is a velocity killer: 9,500 config permutations made it impossible to test combinations or ship without breaking changes
• Press claimed 20% of OpenClaw shells were malicious; the actual figure was 0.3% — but the security narrative still crushed months of momentum
• Fun is velocity: the weeks he enjoyed building, the product visibly improved; the weeks he didn't, they just shipped config options

Part of Issue Nº 004: OpenClaw's near-burnout, agent teams that ship 99.9% of PRs, and the math behind prompt caching