Conference Presentation, Fireside Chat
Peter Steinberger: What Happens When 4.7 Million People Let It Cook
Product Origins and Evolution
- The project began in November 2024 as a personal tool to automate sending prompts from a phone to a computer, evolving into a WhatsApp relay after the founder was annoyed by the lack of existing solutions.
- The software was renamed from "Var Relay" to "Claudius" and eventually "OpenClaw" after a friend submitted a pull request for Discord support.
- Early development relied on Opus 3 and Gemini 2.5, with a specific focus on making the agent feel proactive rather than just a terminal interface.
- The founder adjusted model weights slightly outside default distributions to create a more "friendly" interaction style.
- The project went viral in early January 2025 after a Discord server launch where users hacked and interacted with the agent while the founder slept.
Growth Metrics and Community Impact
- Within eight months, the project attracted over 18,000 unique individuals who opened issues or pull requests.
- Total interactions reached 111,000, with nearly 3,000 distinct contributors making commits to the repository.
- Weekly download counts bottomed out at 835,000 in May before peaking at 4.7 million following the founder's public declaration of the project's independence.
- The project's success led to media attention, Mac Mini stockouts, and a flood of inquiries from reporters and security researchers.
Strategic Decisions and Business Model
- The founder chose to remain independent rather than accept venture capital or a large acquisition, prioritizing personal brand over selling the product.
- The business model shifted from reliance on proprietary models like Opus to supporting open-weight models after a competitor (referred to as "the anime girl company") disabled a subscription dependency.
- A 501(c)(3) non-profit status was established to support the project, with early funding and security infrastructure support from Nvidia.
- The founder admitted to initially struggling with the transition from solo developer to managing a community, leading to a period where the product felt less fun to build.
Security Challenges and Mitigation
- Initial press coverage falsely claimed 20% of agent skills were malicious; the founder published a paper correcting this figure to 0.3% based on a scan of 67,000 instances.
- The team implemented sandboxing, allow lists, and a web protocol with built-in permissions to harden the codebase against security risks.
- Security researchers were identified as a source of stress, with many reports generated by the agents themselves without human testing.
- The project faced criticism for adding excessive configuration options, reaching nearly 9,500 permutations, which made comprehensive testing difficult.
Technical Architecture and Future Roadmap
- The vision is to move from text-only interfaces to voice and multimodal interactions, with recent hacks enabling FaceTime capabilities.
- Future goals include developing a system where agents can run perpetually across team servers with shared session awareness.
- The founder advocates for "graph" or "loop" designs as the next evolution of automation, emphasizing that these are extensions of existing automation concepts rather than new paradigms.
- Current infrastructure bottlenecks include a lack of reliable, cross-platform (especially Mac) test environments for managing distributed agent fleets.
Lessons and Advice for Builders
- The founder advises that "fun" is a critical driver of velocity and product quality; periods of stress and lack of enjoyment correlated with slower progress and feature bloat.
- Personal brand is more valuable than any single product because products can be forked or cloned, but a reputation cannot.
- Developers should prioritize solving their own problems and ensuring they are the first user of their creation.
- The founder recommends writing a
vision.mdfile to maintain project direction and resist the temptation to merge PRs that deviate from the core mission. - Code review is now viewed as risk management rather than a requirement to read every line of code, focusing instead on observation and gut feeling.
- A significant market gap exists for affordable, fast, and reliable Mac-based test environments for AI developers.